I thought that catchup=False currently determines both the first DAG run as well as what happens when a DAG has been paused and missed multiple schedule intervals. In other words, if catchup=False and a daily DAG is paused for a week, then when it is unpaused it would only run the most recently missed DAG run and not run the others from earlier. I tested on 2.2.4 and that was the result.
In that case, the solution to support the three options could handle both scenarios also. On Tue, Mar 22, 2022 at 4:57 PM Daniel Standish <daniel.stand...@astronomer.io.invalid> wrote: > One concern I have with the idea of catchup="none" vs catchup="last" is, > it really only controls what is the first run for the dag; other than that > there is not one bit of difference. E.g. if you have some runs on a daily > dag, and you pause it for a week, when you turn it back on, they both do > the exact same thing. In part because of this it feels like catchup is not > the right place to locate this control. The question of "what will be the > first run" seems like it might more properly located with (1) the > start_date and (2) the schedule (i.e. the timetable). >
