You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Currently, catchup=False means "first run after turning on will be the latest scheduled run" and there is no way to produce the behavior where turning on a DAG means "make the first run after turning on occur at the next schedule time instead of the previous one".
Proposal: make a new flag (call it something to the effect of no_catchup_means_no_past_runs) which when set to True means that turning on a DAG that has the setting catchup=False will result in the first run being the one on the schedule that occurs next in time (rather than the one that occurs in the most recent past).
Use case/motivation
The use case is whenever you want to turn on a DAG without it running right away.
Committer
I acknowledge that I am a maintainer/committer of the Apache Airflow project.
The text was updated successfully, but these errors were encountered:
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.
I doubt we want to add even more complexity and new flag. You can attempt to make a PR to add that and see how complex it would be - I guess pretty complex, but what you should do is to set start_date properly on your DAG when you create it - to start at the date you want it.
Body
Description
Currently, catchup=False means "first run after turning on will be the latest scheduled run" and there is no way to produce the behavior where turning on a DAG means "make the first run after turning on occur at the next schedule time instead of the previous one".
Proposal: make a new flag (call it something to the effect of no_catchup_means_no_past_runs) which when set to True means that turning on a DAG that has the setting catchup=False will result in the first run being the one on the schedule that occurs next in time (rather than the one that occurs in the most recent past).
Use case/motivation
The use case is whenever you want to turn on a DAG without it running right away.
Committer
The text was updated successfully, but these errors were encountered: