Data Interval and Logical Date

An Airflow data interval describes the time range assigned to a run by its scheduling context. A logical date is a scheduling identifier, not the instant a worker begins executing. Their interpretation depends on the timetable and trigger type.

With a UTC daily CronDataIntervalTimetable, the interval from October 1 midnight to October 2 midnight becomes eligible at its end, and the logical date is October 1 midnight. Filtering with start <= timestamp < end places a boundary event in exactly one adjacent interval.

A delayed attempt must still use its assigned range. Eligibility does not establish that all source events have arrived. Manual, asset-driven, and trigger-based schedules may use different interval conventions; validate the context rather than treating every run as yesterday. A local calendar day across daylight-saving changes need not last 24 hours.

See Apache Airflow Fundamentals: DAGs, Tasks, and Scheduling for worked examples.

Reference: Apache Airflow 3.1.0 — Timetables.