seanmuth opened a new pull request, #73689: URL: https://github.com/apache/airflow/pull/73689
When a Dag Run is created while its Dag is already at `max_active_runs` (for example, a second manual trigger while an earlier run is still active), no log message anywhere explains why it never starts. The scheduler's periodic max_active_runs check (enhanced by #72403) only logs the moment a Dag *newly* becomes blocked — not for a run created afterward while it's already blocked, since the promotion query filters it out before that code path is ever reached. This adds a one-shot info log at `DagRun` creation time (`SerializedDAG.create_dagrun`) when the new run will not be immediately schedulable, so the information is available right away without correlating scheduler internals. Part of #73686, which tracks the two related follow-ups (exposing this state via the API, and a UI tooltip) as separate PRs. related: #72387, #72403 --- ##### 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]
