Updated verbiage for backfill runs being deprioritized#67338
Conversation
|
Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide
|
| }, | ||
| "banner": { | ||
| "backfillInProgress": "Backfill in progress", | ||
| "backfillInProgress": "Backfill in progress, backfill runs may get delayed as non-backfill runs takes priority over backfill runs in each scheduler cycle.", |
There was a problem hiding this comment.
I think it would be helpful to put this in a tooltip. It takes up a lot of space in the banner.
|
@g-dailey — There is 1 unresolved review thread on this PR from Note: This comment was drafted by an AI-assisted triage tool and may contain mistakes. Once you have addressed the points above, an Apache Airflow maintainer — a real person — will take the next look at your PR. We use this two-stage triage process so that our maintainers' limited time is spent where it matters most: the conversation with you. |
pierrejeambrun
left a comment
There was a problem hiding this comment.
Good idea.
Just one suggestion from Brent to try to make save some real estate on the page but other than this that's a nice improvement :)
pierrejeambrun
left a comment
There was a problem hiding this comment.
Static check are failing and need fixing. (imports orders)


Adds UI messaging to inform users that backfill DAG runs are
deprioritized behind scheduled and manual runs in the scheduler loop.
Backfill runs have always been lower priority than non-backfill runs due
to how the scheduler orders DAG runs each cycle, but this was not
communicated anywhere in the UI. Users were left confused when backfill
runs remained in a queued/scheduled state longer than expected.
This PR surfaces that context in two places:
This is what the new banner looks like:

Closes: #66729