Updated verbiage for backfill runs being deprioritized#67338
Open
g-dailey wants to merge 1 commit into
Open
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
|
bbovenzi
reviewed
May 22, 2026
| }, | ||
| "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.", |
Contributor
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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