You are deploying an orchestration platform to automate hourly data-ingestion pipelines. A six-hour network outage prevents the 03:00-08:00 runs from executing. When connectivity returns, the business wants the orchestrator to automatically create and execute pipeline instances for each missed hour in chronological order, with no manual triggers or code changes. Which built-in orchestration capability is specifically designed to satisfy this requirement?
Catch-up (backfill) scheduling that automatically creates runs for every missed time interval
Service-level-agreement (SLA) miss callbacks that fire alerts when a task runs too long
Branching operators that choose between alternative execution paths during the workflow
Dynamic task mapping that expands a single task into parallel subtasks at runtime
Most workflow-orchestration tools (for example, Apache Airflow, Prefect, and Dagster) provide a catch-up or backfill feature. When enabled, the scheduler inspects the schedule for any intervals that have not yet been processed and automatically generates separate pipeline (DAG/flow) runs for each missing interval. Those runs are queued and executed in timestamp order, honoring task dependencies exactly as they would have run originally. Dynamic task mapping, branching, and SLA-miss callbacks are unrelated: they affect how individual tasks behave, not how the scheduler recovers entire missed pipeline intervals. Therefore, enabling catch-up/backfill directly meets the requirement to re-run all six missed hourly pipelines without manual intervention.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is 'catch-up' (backfill) scheduling in an orchestration tool?
Open an interactive chat with Bash
What is the difference between catch-up scheduling and dynamic task mapping?
Open an interactive chat with Bash
How does catch-up scheduling maintain task dependencies?