alejandrofm opened a new issue, #29524: URL: https://github.com/apache/airflow/issues/29524
### Apache Airflow version Other Airflow 2 version (please specify below) ### What happened Currently on 2.4.2 When some tasks of a run fail and the next start we can have this situation: - All green on the first run, but 1 red, run status = Failed - Next run starts and executes everything but the task that had an error before, which stays with the status None and the task is still on status Running. - I clear the failed tasks of the first run, but the run doesn't execute because the max_active_runs property is maxed, for example, 1/1. Result: The DAG gets deadlocked and needs to mark the first run as success for the second to finish and then clear the previous one for it to start running the cleared tasks. ### What you think should happen instead When runs == max_active_runs and depends_on_past == True and there are tasks with status=None (Cleared) on previous runs, the current run has to stop and give resources to the run that is locking the current. ### How to reproduce Set DAG config as: max_active_runs == 1 depends_on_past == True Start two runs, and mark some tasks on the first as failed. This can happen with a higher value of max_active_run too, but 1 is the easiest to reproduce. ### Operating System Linux image ### Versions of Apache Airflow Providers _No response_ ### Deployment Official Apache Airflow Helm Chart ### Deployment details _No response_ ### Anything else _No response_ ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
