-
Notifications
You must be signed in to change notification settings - Fork 17k
Regression: "Mark state as..." button options grayed out #66197
Copy link
Copy link
Open
Labels
area:UIRelated to UI/UX. For Frontend Developers.Related to UI/UX. For Frontend Developers.area:corekind:bugThis is a clearly a bugThis is a clearly a bugneeds-triagelabel for new issues that we didn't triage yetlabel for new issues that we didn't triage yetpriority:mediumBug that should be fixed before next release but would not block a releaseBug that should be fixed before next release but would not block a release
Metadata
Metadata
Assignees
Labels
area:UIRelated to UI/UX. For Frontend Developers.Related to UI/UX. For Frontend Developers.area:corekind:bugThis is a clearly a bugThis is a clearly a bugneeds-triagelabel for new issues that we didn't triage yetlabel for new issues that we didn't triage yetpriority:mediumBug that should be fixed before next release but would not block a releaseBug that should be fixed before next release but would not block a release
Type
Fields
Give feedbackNo fields configured for issues without a type.
Under which category would you file this issue?
Airflow Core
Apache Airflow version
3.1.7
What happened and how to reproduce it?
The same problem as #36219, which has returned in Airflow 3.x.
The button to mark a task state or a DAGRun state as success is grayed out when the task or DAGRun is already in a success state. Conversely, whenever a task or DAGRun is in a failed state, the mark as failed button is grayed out.
How to reproduce: Mark a task or DAGRun as success. Then try to do it again.
What you think should happen instead?
For tasks: these buttons bring up another dialog where you may select past/future/downstream/upstream tasks. These tasks may not match the state of the task you currently have selected. Frequently it is useful to be able to set all up/downstream tasks of an already succeeded/failed task to success/failed respectively.
For DAGRuns: A DAGRun in the success state may contain failed tasks for various reasons. You want to be able to set the DAGRun and all of its tasks to success, but this is not possible without flipping the state to failed first, and then back to success.
These buttons should not be grayed out.
Operating System
No response
Deployment
None
Apache Airflow Provider(s)
No response
Versions of Apache Airflow Providers
No response
Official Helm Chart version
Not Applicable
Kubernetes Version
No response
Helm Chart configuration
No response
Docker Image customizations
No response
Anything else?
No response
Are you willing to submit PR?
Code of Conduct