potiuk commented on issue #31937: URL: https://github.com/apache/airflow/issues/31937#issuecomment-1597219948
> I think I speak for a lot of people from my experience and colleagues that when I set catchup to false and set a schedule of f.e. `0 4 * * *` and enable my DAG I intended for it to run on the next day at 4 AM not as soon as I enable it. Why not set start_date in the future, when you want to start it ? That's non-ambiguous, and very clearly describes your intention. Basing when the first run should run the fact when you "enable" it in the UI seems lika spreading the schedule definition not only between two places (DAG + UI) but also making it dependent on when one of the users (without really tracking it) perform certain action. It's enough "variability" to have 'catchup=False` to decide based on the user actions. My feeling is that maybe we shoud just communnicate it better that schedule + start_date is the way how your schedule definition looks like. I think just explaining that "if you want to control start_date of your DAG, it should be in the dag definition". Just detecting if the DAG has no start_date / start_date in the past and catchup=false, the "Enable" button should have an information that it will start running immediately, unless you specify start_date in the future that limits it. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
