Scheduling for Apache Airflows
Airflow scheduling controls when DAG runs are created. A schedule can be a cron expression, a preset or a timetable, and each run covers a data interval with a logical date. Catchup and backfills decide whether missed intervals are run, which matters for correct reprocessing of historical data.
Stage: Authoring and Scheduling · Part of the Apache Airflow roadmap · Last reviewed 19 November 2026
What to learn in Scheduling
- Set a schedule with a cron expression or a preset
- Explain the data interval and logical date of a DAG run
- Control catchup behaviour and run a backfill
- Use the data interval start and end in a templated query
- Predict when the first run of a new DAG will start
Scheduling interview questions
Why does an Airflow run start after its data interval ends?
A DAG run for an interval processes the data that arrived during that interval, so it can only start once the interval is complete. A daily run for Monday begins at the start of Tuesday. This confuses beginners who expect it to run at the interval start.
What does catchup do?
When catchup is enabled, Airflow creates runs for every schedule interval between the start date and now that has not run yet, such as when you deploy an old start date or unpause after downtime. Setting catchup to False runs only the latest interval.
Where Scheduling fits in the Apache Airflow roadmap
Scheduling belongs to the Authoring and Scheduling stage (intermediate level). Build workflows.
Other units in this stage
Back to the full Apache Airflow roadmap