Hello Airflow dev community, What would you think about making the first dag run optional when catchup is false, as it is currently the case ( described here: https://airflow.apache.org/docs/apache-airflow/stable/dag-run.html#catchup). I could be done through an additional, explicit, flag but I would like to talk about the concert first before the implementation details.
I know there is a workaround to set the start date between the last interval and now, but not everyone can dynamically change the start date at each DAG deployment. In my opinion, catchup false should mean "I do not want to catch up with past instances", which would exclude the last data interval as it is part of the past. It should only look forward and trigger on the next match. It is the typical behavior users would expect when porting their CRON jobs to Airflow for instance. Unless I am completely missing something about this first dag run? Thank you, Regards, Philippe
