andreychernih opened a new issue #20461: URL: https://github.com/apache/airflow/issues/20461
### Apache Airflow version 2.2.2 ### What happened I have a DAG which start_date was 09/01/2021 initially but then it was changed to 11/01/2021. This DAG has some runs prior to 11/01/2021 that did not get a chance to finish. I can now see that scheduler is still trying to schedule the runs prior to 11/01/2021. But none of the tasks in these runs are starting because of the start_date check I presume. This is maxing out the active runs thus blocking any other days within the DAG range to be scheduled. <img width="1335" alt="Screen Shot 2021-12-22 at 7 56 22 AM" src="https://user-images.githubusercontent.com/131281/147105749-cc32bfe4-33b1-46fc-8cca-f5e31c92b0e0.png"> <img width="992" alt="Screen Shot 2021-12-22 at 7 56 29 AM" src="https://user-images.githubusercontent.com/131281/147105764-857d0f85-2877-4ae5-b568-7cbf21c6ca48.png"> ### What you expected to happen Scheduler should not be trying to schedule runs that are prior to DAG's start_date. ### How to reproduce _No response_ ### Operating System Airflow Docker ### Versions of Apache Airflow Providers _No response_ ### Deployment Other Docker-based deployment ### 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]
