So the cost with this configurable with something like this ... Catchup=True : run all intervals Catchup=False: do not run any past interval Catchup="Last Interval" (or any better name :))
... is that it adds complexity to the interface. Not necessarily saying it's not worth the cost, but it ain't free. This is more to document, more for users to have to discover and keep in their minds, more edge cases to handle in the scheduler etc. And it's quite a subtle distinction. I haven't had a chance to fully think through this specific proposal but just wanted to put it out there that there are tradeoffs when you do something like this and more configurability isn't always better. Especially *if* airflow already provides the "language" to express the desired behavior, or *if* we can reasonably just change the behavior instead of making it configurable.
