This path is for you if someone said DAG and meant a schedule, not a philosophy. Two parts: a first DAG as a rail of tickets, then retries, sensors, and when Airflow is the wrong tool. Start with the first part on this page. If you only need the idea of orchestration, the pipelines series says it in one metaphor.
- 1 Airflow hello: your first DAG as a ticket rail Orchestration is a ticket rail, not a junk drawer. Learn what an Airflow DAG is, how tasks and dependencies map to real runbook stations, and how to sketch a first daily orders rail you can actually operate.
- 2 Airflow hello: retries, sensors, and when not to use it Retries buy time for flukes; sensors encode waiting with deadlines. Learn when to retry, how to sensor a late file without burning workers, and when Airflow is the wrong tool for the job.