uranusjr commented on issue #14299: URL: https://github.com/apache/airflow/issues/14299#issuecomment-839375820
This happens when `catchup=False`. The calculation mutates the DAG instance here: https://github.com/apache/airflow/blob/6690758c696562e0fd4f1858d937d43efd1fbb47/airflow/models/dag.py#L580-L584 because when there’s no catchup, we don’t want to schedule the DAG for periods before the current time. So the displayed time is *logically* correct to the scheduler—the DAG won’t actually start being scheduled until the logical start date, even if the user set the value to an earlier time—but probably not what the user expects (as this issue shows). So the current start date isn’t wrong (in a sense); confusing terminology is a good description. Simply changing the start date to show the value specified by the user is also misleading IMO because the DAG detail page won’t be able to reflect `catchup=False`, and the user will be confused why the DAG is not being scheduled after the start date. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
