UI: Show deactivated state for stale DAGs#65214
Merged
pierrejeambrun merged 1 commit intoApr 14, 2026
Merged
Conversation
When a DAG becomes stale or deactivated, the UI still shows active-oriented controls like the pause toggle, parse action, and next-run information. This change makes the deactivated state explicit by showing a badge and hiding controls that imply the DAG is still schedulable. - Add reusable DagDeactivatedBadge component - Show badge instead of pause toggle for stale DAGs in header and breadcrumb - Hide next-run stat and parse action for stale DAGs - Add regression test for stale DAG header behavior Fixes apache#63800
pierrejeambrun
requested review from
bbovenzi,
guan404ming,
ryanahamilton and
shubhamraj-git
as code owners
pierrejeambrun
requested review from
choo121600 and
vatsrahul1001
as code owners
boring-cyborg
Bot
added
area:translations
area:UI
eladkal
approved these changes
Apr 14, 2026
Member
Author
|
github-actions Bot
pushed a commit
that referenced
this pull request
Apr 14, 2026
When a DAG becomes stale or deactivated, the UI still shows active-oriented controls like the pause toggle, parse action, and next-run information. This change makes the deactivated state explicit by showing a badge and hiding controls that imply the DAG is still schedulable. - Add reusable DagDeactivatedBadge component - Show badge instead of pause toggle for stale DAGs in header and breadcrumb - Hide next-run stat and parse action for stale DAGs - Add regression test for stale DAG header behavior Fixes #63800 (cherry picked from commit 2d42641) Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com>
Contributor
Backport successfully created: v3-2-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
pierrejeambrun
added a commit
that referenced
this pull request
Apr 14, 2026
When a DAG becomes stale or deactivated, the UI still shows active-oriented controls like the pause toggle, parse action, and next-run information. This change makes the deactivated state explicit by showing a badge and hiding controls that imply the DAG is still schedulable. - Add reusable DagDeactivatedBadge component - Show badge instead of pause toggle for stale DAGs in header and breadcrumb - Hide next-run stat and parse action for stale DAGs - Add regression test for stale DAG header behavior Fixes #63800 (cherry picked from commit 2d42641) Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com>
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 15, 2026
When a DAG becomes stale or deactivated, the UI still shows active-oriented controls like the pause toggle, parse action, and next-run information. This change makes the deactivated state explicit by showing a badge and hiding controls that imply the DAG is still schedulable. - Add reusable DagDeactivatedBadge component - Show badge instead of pause toggle for stale DAGs in header and breadcrumb - Hide next-run stat and parse action for stale DAGs - Add regression test for stale DAG header behavior Fixes #63800 (cherry picked from commit 2d42641) Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com>
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 15, 2026
When a DAG becomes stale or deactivated, the UI still shows active-oriented controls like the pause toggle, parse action, and next-run information. This change makes the deactivated state explicit by showing a badge and hiding controls that imply the DAG is still schedulable. - Add reusable DagDeactivatedBadge component - Show badge instead of pause toggle for stale DAGs in header and breadcrumb - Hide next-run stat and parse action for stale DAGs - Add regression test for stale DAG header behavior Fixes #63800 (cherry picked from commit 2d42641) Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com>
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 15, 2026
When a DAG becomes stale or deactivated, the UI still shows active-oriented controls like the pause toggle, parse action, and next-run information. This change makes the deactivated state explicit by showing a badge and hiding controls that imply the DAG is still schedulable. - Add reusable DagDeactivatedBadge component - Show badge instead of pause toggle for stale DAGs in header and breadcrumb - Hide next-run stat and parse action for stale DAGs - Add regression test for stale DAG header behavior Fixes #63800 (cherry picked from commit 2d42641) Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com>
vatsrahul1001
pushed a commit
that referenced
this pull request
Apr 15, 2026
When a DAG becomes stale or deactivated, the UI still shows active-oriented controls like the pause toggle, parse action, and next-run information. This change makes the deactivated state explicit by showing a badge and hiding controls that imply the DAG is still schedulable. - Add reusable DagDeactivatedBadge component - Show badge instead of pause toggle for stale DAGs in header and breadcrumb - Hide next-run stat and parse action for stale DAGs - Add regression test for stale DAG header behavior Fixes #63800 (cherry picked from commit 2d42641) Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com>
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
2 participants
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.
Re-opening of #64374 (closed unexpectedly by original contributor). Formatting issue fixed.
Summary
When a DAG becomes stale or deactivated, the UI still shows active-oriented controls like the pause toggle, parse action, and next-run information. This change makes the deactivated state explicit by showing a badge and hiding controls that imply the DAG is still schedulable.
Changes
DagDeactivatedBadge.tsx— reusable badge component for stale/deactivated DAGsHeader.tsx— shows deactivated badge for stale DAGs, hides next-run stat and parse actionDagBreadcrumb.tsx— shows deactivated badge instead of pause toggle for stale DAGsDetailsLayout.tsx— removes unnecessary generic type annotations onuseLocalStoragedag.json— adds the "Deactivated" i18n labelHeader.test.tsx— regression test for stale DAG header behaviorFixes #63800
Was generative AI tooling used to co-author this PR?
Generated-by: Cursor (Claude Opus 4) following the guidelines