# Airflow DAG Run

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

**Field:** Data Engineering  
**Category:** Orchestration  
**Also known as:** DAG Run, Logical Date, Data Interval

## Think of it like

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

## 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.

## 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.

## 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.

## Three principles

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

## Related terms

- [Airflow DAG](https://learn.benibix.com/term/data/airflow-dag)
- [Data Backfill](https://learn.benibix.com/term/data/data-backfill)
- [Idempotent Pipeline](https://learn.benibix.com/term/data/idempotent-pipeline)
- [Workflow Scheduler](https://learn.benibix.com/term/data/workflow-scheduler)
- [Airflow Catchup](https://learn.benibix.com/term/data/airflow-catchup)

## Told apart from

- [Airflow DAG vs DAG Run](https://learn.benibix.com/compare/airflow-dag-vs-airflow-dag-run): People say DAG when they mean one run of it, and the two are not the same. An Airflow DAG is the pipeline itself: a Python file with tasks, arrows and a schedule. A DAG run is one time that pipeline ran, tied to one date of data. One daily DAG makes 365 runs a year, and each run can pass or fail on its own.

![An operator box labelled BashOperator becomes a task called load_orders inside a DAG. Below it, three DAG runs for 1, 2 and 3 March each hold one task instance with its own status: success, success and running. The third run also shows an XCom carrying a file path.](https://learn.benibix.com/diagrams/airflow-operator-task.svg)

---

Source: https://learn.benibix.com/term/data/airflow-dag-run
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-17
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
