Vamsi-klu opened a new pull request, #71992: URL: https://github.com/apache/airflow/pull/71992
Leftover asset events 2, 3, and 4 that arrive while a Dag is at `max_active_runs=1` must stay in ADRQ and all be consumed by the next run. Event 5 is its own run. A stale `exceeds_max_non_backfill` flag no longer hides a Dag that has queued events. The cached flag now applies only to timetable-due Dags. Asset create sets the flag after `create_dagrun`. Live QUEUED+RUNNING exclusion still defers Dags at cap and does not delete ADRQ. This is batch leftovers, not the one-run-per-event redesign in #56750. closes: #56050 Related: mapped consume-all coverage is #54659. ## Test plan - [x] leftover consume + event 5 + empty stale ADRQ in `test_scheduler_job.py` - [x] `test_dags_needing_dagruns_assets*` including stale-flag True, 0 active, 3 ADRQ --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Cursor Grok 4.6 Generated-by: Cursor Grok 4.6 following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) Made with [Cursor](https://cursor.com) -- 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]
