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).
- Re: Make first dag run optional when catchup is False Constance Martineau
- Re: Make first dag run optional when catchup is False Philippe Lanoe
- Re: Make first dag run optional when catchup is False Jarek Potiuk
- Re: Make first dag run optional when catchup is False Jarek Potiuk
- Re: Make first dag run optional when catchup is False Daniel Standish
- Re: Make first dag run optional when catchup is False Daniel Standish
- Re: Make first dag run optional when catchup is False Daniel Standish
- Re: Make first dag run optional when catchup is False Collin McNulty
- Re: Make first dag run optional when catchup is False Daniel Standish
- Re: Make first dag run optional when catchup is False Constance Martineau
- Re: Make first dag run optional when catchup is False Daniel Standish
- Re: Make first dag run optional when catchup is False Larry Komenda
- Re: Make first dag run optional when catchup is False Daniel Standish