sivieri opened a new issue, #24279: URL: https://github.com/apache/airflow/issues/24279
### What do you see as an issue? Looking at the [documentation](https://airflow.apache.org/docs/apache-airflow/stable/concepts/dags.html#concepts-trigger-rules) about trigger rules, it is not clear how the `upstream_failed` status is transmitted downstream. The documentation contains several details about how the rules behave with skipped tasks, but no information (that I could find) is dedicated to `upstream_failed`, which is equally important in my opinion. For instance, from past experience I understand that: - a task with multiple upstream dependencies and `all_success` is immediately executed as soon as one of the upstream tasks fails (or upstream-fails due to its own upstream dependencies), and it goes into a failed state - a task with multiple upstream dependencies and `all_done` does wait for all upstream dependencies, regardless of the fact that one of them has `upstream_failed`, and it is fully executed, it does not go automatically into a failed state. The use case that prompted my question is the fact that I have a task with multiple upstream dependencies, and if one of those fails or receives an upstream failure (and goes into `upstream_failed`), it should wait for all the other dependencies to arrive at some state before being executed (and failing as well, so `all_done` would not be enough). ### Solving the problem If possible, it would be nice to have a section, similar to the skipped tasks one, that explains how the failures (and upstream failures) are transmitted down the graph. ### Anything else _No response_ ### Are you willing to submit 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
