deepak4babu opened a new issue, #60764: URL: https://github.com/apache/airflow/issues/60764
### Apache Airflow version Other Airflow 3 version (please specify below) ### If "Other Airflow 3 version" selected, which one? 3.0.6 ### What happened? When stale dags are not deactivated, then airflow scheduler gives errors like below. Eventually, the number of dagruns created by airflow is reduced and the overall throughput decreases. ### What you think should happen instead? Airflow scheduler should ignore the dags that is not in serialized table and create dagruns for others. ### How to reproduce Create a 2.x airflow environment with 10+ dags. Make sure the multiple dagruns can run concurrently for all dags. Upgrade airflow to 3.0.6 and at the same time remove atleast 5 dags during the upgrade. Airflow will eventually stops scheduling dagruns for the other dags ### Operating System Debian GNU/Linux 12 (bookworm) ### Versions of Apache Airflow Providers apache-airflow-providers-celery==3.12.2 apache-airflow-providers-cncf-kubernetes==10.8.2 apache-airflow-providers-common-compat==1.7.3 apache-airflow-providers-common-io==1.6.2 apache-airflow-providers-common-sql==1.27.5 apache-airflow-providers-fab==2.4.1 apache-airflow-providers-ftp==3.13.2 apache-airflow-providers-http==5.3.3 apache-airflow-providers-imap==3.9.2 apache-airflow-providers-postgres==6.2.3 apache-airflow-providers-smtp==2.2.0 apache-airflow-providers-sqlite==4.1.2 apache-airflow-providers-standard==1.6.0 ### Deployment Other ### 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]
