Skip to content
BENIBIX Learn

Airflow Catchup

Data🗓️ OrchestrationApache Airflow

Also known as Catchup, catchup=True, catchup_by_default

Whether Airflow runs each missed day when a DAG is switched on. Or just the last one.

Think of it like

It is like being away for a week. Do you do all the missed homework, or just today's?

Example

A daily DAG with a start date in January is switched on in March. With catchup on, Airflow makes about 60 runs at once. With it off, it makes one.

Why it matters

It decides whether one click starts one run or hundreds. Hundreds of runs at once can flood a database.

Definition

Catchup decides what Airflow does with runs it missed. A DAG may be switched on days after its start date. With catchup on, the scheduler makes one run for each missed time, oldest first. With catchup off, it makes only the latest run and skips the rest. In current Airflow, catchup is off unless you turn it on. You set it on each DAG.

Example code

python
@dag(schedule="@daily",
     start_date=pendulum.datetime(2026, 1, 1, tz="UTC"),
     catchup=False)
Catchup is off, so Airflow runs only the latest day. It skips the days since January.
With catchup on, every missed day runs. With it off, only the latest day runs.

Common mistake

Turning catchup on to fill old dates by accident. Use a planned backfill instead, so you choose the dates.

Key takeaways

  1. 1
    Missed runs. Dates between start and now.
  2. 2
    On or off. All of them, or only the latest.
  3. 3
    Per DAG. Each DAG sets its own.

Compare