Skip to content
BENIBIX Learn

Airflow DAG Run

Data🗓️ OrchestrationApache Airflow

Also known as DAG Run, Logical Date, Data Interval

One run of an Airflow DAG. It is tied to the date of its data.

Think of it like

The recipe is the DAG. Each time you cook it is a run, with its own date on the label.

Example

On 4 March at 6 am, Airflow starts the run for 3 March. It loads the whole of 3 March, which is now complete.

Why it matters

The logical date is how a rerun of an old day reads the right data. It is also how a backfill makes one run per missing day.

Definition

A DAG run is one run of an Airflow DAG, from its first task to its last. Each run has a logical date, which says which slice of time it covers. A daily run for 3 March covers that day's data, even if it starts the next morning. Every task in the DAG gets its own task instance inside the run. A run can be started by the schedule, by a person or by a backfill.
Each DAG run is one column, stamped with the date of the data it covers.

Common mistake

Using the current time inside a task instead of the run's date. A rerun of last Tuesday then loads today's data.

Key takeaways

  1. 1
    One run, one slice. Each run covers a set stretch of time.
  2. 2
    Logical date. The date of the data, not the clock.
  3. 3
    Many starters. A schedule, a person or a backfill.

Compare