The "Set state to success" in the Task Instances view behaves differently than "Mark state as.. (success)" in Dag's detail view.

[Pad71]

Apache Airflow version

2.9.0

If "Other Airflow 2 version" selected, which one?

No response

What happened?

Dag's detail view

• action "Mark state as... (Success)" set task instance state to Success and clear downstream tasks.

Task instance view

• action "Set state to success" set task instance state to Success, but it does not clear downstream tasks. So if there any downstream tasks in the "upstream failed" state, you have to solve it separately. I think, it should behave similar to "Mark state as.. (success)" above.

What you think should happen instead?

The action "Set state to Success" in the task instance view should clear downstream tasks.

How to reproduce

Prerequisity:
Dagrun with the failed task, which has the downstream tasks in the "upstream failed" state.

Open Task Instance View, find failed task and use action "Set State to Success"

Operating System

Kubernetes on Unix platform

Versions of Apache Airflow Providers

No response

Deployment

Official Apache Airflow Helm Chart

Deployment details

No response

Anything else?

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct