roykoand opened a new issue, #69765: URL: https://github.com/apache/airflow/issues/69765
### Under which category would you file this issue? Providers ### Apache Airflow version 3.2.2 ### What happened and how to reproduce it? The "Max active runs" counter in the DAG detail page header (displayed as "X of Y") counts both `Running` and `Queued` Dag runs. However, `max_active_runs` is only enforced by the scheduler against `Running` runs. This makes the UI misleading — after a backfill, the counter can show a number far exceeding the configured limit (e.g. 12 of 5), even though the scheduler is behaving correctly. <img width="2925" height="463" alt="Image" src="https://github.com/user-attachments/assets/9f8f6bf6-3332-4224-bd81-bfe38418e1f5"; /> ### What you think should happen instead? The counter should show only `Running` Dag runs matching exactly what the scheduler enforces. A user looking at 3 of 5 should be able to interpret it as "3 slots taken, 2 available" — which is only true if queued runs are excluded. ### Operating System _No response_ ### Deployment None ### Apache Airflow Provider(s) _No response_ ### Versions of Apache Airflow Providers _No response_ ### Official Helm Chart version Not Applicable ### Kubernetes Version _No response_ ### Helm Chart configuration _No response_ ### Docker Image customizations _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]
