jtreffler opened a new issue, #56646: URL: https://github.com/apache/airflow/issues/56646
### Apache Airflow version Other Airflow 2/3 version (please specify below) ### If "Other Airflow 2/3 version" selected, which one? 3.0.6 ### What happened? If I configure max_active_runs_per_dag = 1 , catchup = true and schedule a dag in short cycles i see following behaviour. On first run it starts one dag run and the creates the rest of the runs which are up to come as queued. Once the first run is finished it starts all runs which are not yet started in parallel (see screenshot) <img width="2229" height="1207" alt="Image" src="https://github.com/user-attachments/assets/4a9bb799-dc1c-450b-8d8a-66b1656be9f4"; /> We have same behaviour if we clear tasks backwards to recalculate some days. ### What you think should happen instead? the Dag runs should be triggered one after another in correct order, otherwise you can produce huge data issues in cases you have calculations which needs to go in correct timed order ### How to reproduce create a dag which will trigger every hour, catchup true, start date should be today or yesterday, configure max_active_runs_per_dag = 1 and enable the dag... ### Operating System ubi9/python312 ### Versions of Apache Airflow Providers n/a (pip contract enforced) ### Deployment Official Apache Airflow Helm Chart ### Deployment details we are using self written helm charts for deployment ### 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]
