Show backfill Dag runs in the UI#70159
Draft
shivaam wants to merge 5 commits into
Draft
Conversation
Backfill histories currently expose only high-level configuration, which makes it hard to distinguish scheduled, failed, and skipped slots after a backfill starts.
The user-visible detail page needs an Airflow feature newsfragment.
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.
Use the backfill Dag-run entries API added in #67381 to make the Dag runs associated with a backfill inspectable in the UI.
What changed
Dag > Backfills > Backfill #Nbreadcrumb navigation.Request behavior
Opening the dedicated screen makes two backfill-specific requests:
While the backfill is active and unpaused, both requests follow the configured auto-refresh interval so the duration, completion state, and visible Dag-run statuses stay current. Refreshing stops when the backfill is paused or completed. Changing pages requests only the selected page; the UI never sweeps hidden pages and does not require a new aggregation endpoint.
Pause, unpause, and cancel retain their existing behavior. After a successful action, the affected backfill views are refreshed immediately so they do not display stale state.
Related: #67381
Testing
pnpm lintpnpm test— 95 test files, 696 tests passedpnpm buildbreeze testing ui-e2e-tests --browser chromium --test-pattern backfill.spec.ts -- --workers=1— 8 tests passedWas generative AI tooling used to co-author this PR?
Generated-by: Codex (GPT-5) following the guidelines
Drafted-by: Codex (GPT-5) (no human review before posting)