seanmuth opened a new pull request, #73692:
URL: https://github.com/apache/airflow/pull/73692
`DagModel.exceeds_max_non_backfill` has been persisted since 3.2.0
(migration `0099_3_2_0_add_exceeds_max_runs_flag_to_dag_model`) and is already
used internally by the scheduler to skip re-evaluating Dags that are already at
their `max_active_runs` limit — but it was never exposed anywhere in the public
API. There's currently no way for a client to ask "is this Dag currently
blocked on max_active_runs" without independently computing active-run counts
against the limit.
This exposes it on `GET /dags/{dag_id}/details` as
`exceeds_max_active_runs`, aliased to the underlying model column via the
existing `DAG_ALIAS_MAPPING` mechanism used elsewhere in `DAGDetailsResponse`.
Scoped to the details endpoint (not the list endpoint) to match where
`active_runs_count` already lives, since this is intended to pair with it on
the Dag detail view.
Part of #73686, which also tracks the related UI tooltip follow-up.
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes — Claude Sonnet 5
Generated-by: Claude Sonnet 5 following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
--
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]
