seth-olsen opened a new issue, #45691:
URL: https://github.com/apache/airflow/issues/45691

   ### 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.
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscr...@airflow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to