The catchup=True FloodPipeline · medium · ~12 minA new DAG shipped at 16:00 with start_date=2024-01-01 and Airflow's default catchup=True. The scheduler did what it was told: it queued ~920 historical runs. Within an hour the warehouse pool is saturated, today's SLA-critical pipelines are stuck behind a wall of 2024 backfill tasks, and the warehouse itself is queuing.Stop the flood without losing the history you actually do want.Evidence

Metrics

Evidence

Config

Checkpoints

Immediate triage, in the right order?

The controlled way to get the 2024+ history the team wants?

What defaults/policies stop the next new DAG from doing this? Interview-style.