I agree with this. I'd much rather have to trigger a single manual run the first time I enable a DAG than to either wait to enable until after I want it to run or by editing the start_date of the DAG itself.
I'd be in favor of adjusting this behavior either permanently or by a configuration. On Fri, Mar 4, 2022 at 3:00 PM Philippe Lanoe <[email protected]> wrote: > Hello Daniel, > > Thank you for your answer. In your example, as I experienced, the first > run would not be 2010-01-01 but 2022-03-03, 00:00:00 (it is currently March > 4 - 21:00 here), which is the execution date corresponding to the start of > the previous data interval, but the result is the same: an undesired dag > run. (For instance, in case of cron schedule '00 22 * * *', one dagrun > would be started immediately with execution date of 2022-03-02, 22:00:00) > > I also agree with you that it could be categorized as a bug and I would > also vote for a fix. > > Would be great to have the feedback of others on this. > > On Fri, Mar 4, 2022 at 6:17 PM Daniel Standish > <[email protected]> wrote: > >> You are saying, when you turn on for the first time a dag with >> e.g. @daily schedule, and catchup = False, if start date is 2010-01-01, >> then it would run first the 2010-01-01 run, then the current run (whatever >> yesterday is)? That sounds familiar. >> >> Yeah I don't like that behavior. I agree that, as you say, it's not >> the intuitive behavior. Seems it could reasonably be categorized as a >> bug. I'd prefer we just "fix" it rather than making it configurable. But >> some might have concerns re backcompat. >> >> What do others think? >> >> >>
