cdabella opened a new issue, #27324: URL: https://github.com/apache/airflow/issues/27324
### Description Add `held` as a TaskInstanceState which functions similarly to `failed` but represents a stop in DAG execution that is known and planned. ### Use case/motivation Many DAGs and pipelines have steps that require human intervention and sign-off before continuing, like manual data validation or manager approval before continuation. This can be functionally achieved today by marking a task as `failed`, but operationally overloading the meaning of `failed` can cause issues with Ops/monitoring/alerting that may not have the complete picture to know whether a task has truly failed or has been marked `failed` by design. Adding an additional TaskInstanceState which represents putting a task on-hold improves clarity in DAG design while achieving the functional goal of stopping a DAGRun from continuing. ### Related issues _No response_ ### Are you willing to submit a PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@airflow.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
