Sensor
Instead of guessing that the input has landed, a sensor waits for it. What it costs is a worker slot, some polling, and a deadline you must remember to set.
Instead of guessing that the input has landed, a sensor waits for it. What it costs is a worker slot, some polling, and a deadline you must remember to set.
The 07:00 run usually processes yesterday, not this morning. Naming the interval a run covers is what makes a rerun mean the same thing as the original.
An orchestrator is not a fancier cron. It keeps state per run, enforces order, retries within limits — and still says nothing about whether the data is right.
Running at 07:00 is not the same as running when the data is there. How orchestrators decide what runs, in what order, and what happens when a step fails.
Release workers during supported waiting, distinguish deferral from reschedule mode, and account for triggerer capacity and pool policy.
Limit participating Airflow tasks with weighted pool slots, distinguish concurrency from request rate, and plan how deferred tasks count.
Learn how Airflow timetables define run timing and data intervals, compare trigger and interval schedules, and check time boundaries before deployment.
Separate TaskFlow graph construction from task execution, follow returned values through XCom, and recognize the limits of ordinary Python-looking calls.
Understand how Airflow catchup selects missing intervals, compare it with retries and backfills, and avoid confusing scheduled work with complete data.
Choose which upstream states allow a task to run, distinguish all_success from all_done, and check how leaf tasks affect the overall run status.
Pass small values or versioned data references between Airflow tasks, and separate metadata exchange from durable shared storage.
Use a run’s intended data interval instead of wall-clock time, check boundaries, and account for timetable-specific logical dates.
Track an Airflow task within a run, distinguish attempts from executions, and make repeated destination effects safe before adding retries.
Separate an Airflow workflow definition from each execution, trace task dependencies, and understand why different runs can overlap.