Description

Hello,
There are times when we want to explicitly mark a DAG as FAILED through the Airflow UI.
In such cases, users generally expect the DAG to be forcibly terminated.
However, the DAG continues to run until it completes on its own.
(When using KubernetesPodOperator, the associated pod is not even deleted.)

Is there a reason why the DAG is not forcibly terminated?
We’re not sure if this behavior is by design or a bug.
If it is a bug, we would like to know whether it is something we can report and submit a PR for.

Thank you.

Use case/motivation

No response

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

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