RikHeijdens opened a new pull request #14455: URL: https://github.com/apache/airflow/pull/14455
When clearing the state of Task Instances through the Web UI if the DagRun is in a `FAILED` state, then Airflow will also automatically transition the associated `DagRun` back into the `RUNNING` state. However, if task instances are being cleared in this manner *after* the DagRun has exceeded it's DagRun time out, as calculated by subtracting the `dagrun_timeout` from the current time and comparing that with the DagRun's `start_date`, then this will cause the active scheduler to immediately transition the DagRun back into a `FAILED` state. In most cases this is probably not what the operator wants (why would the operator otherwise clear tasks?). A better approach would be to reset the DagRun's `start_date` and `end_date` when transitioning back to the `RUNNING` state. --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in [UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md). ---------------------------------------------------------------- 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]
