The DAG That Waited ForeverPipeline · easy · ~10 minYour Airflow deployment has ground to a halt. Around 30 DAGs are stuck 'running' but making no progress, and new runs are queued but never start. It began after an upstream vendor delayed a daily file. The daily_revenue DAG's first task — a FileSensor waiting for that file — has been running for 9 hours. Many other DAGs' sensors are stuck too.Figure out why one late file froze the whole scheduler.Evidence

Metrics

Airflow Logs

Config

Checkpoints

Why did one late file stall dozens of unrelated DAGs?

What is the right long-term fix for the sensors?

What would you do RIGHT NOW to unblock the platform, and what's the durable fix? (interview-style)