ElisaWChen commented on issue #17010: URL: https://github.com/apache/airflow/issues/17010#issuecomment-2039920636
> the trigger rule `none_failed_or_skipped` is a solution to your use case -> https://airflow.apache.org/docs/apache-airflow/2.1.2/concepts/dags.html?highlight=none_failed_or_skipped#trigger-rules > > ```python > task_at_least_one_previous_succeed = SomeOperator( > trigger_rule = "none_failed_or_skipped", > ... > ) > > [task_a,task_b,task_c] >> task_at_least_one_previous_succeed > ``` In case anyone finds this thread in the future like myself, I'm using Airflow 2.4.3 and I tested `'none_failed_or_skipped'` and it did not in fact have the behavior that this thread seemed to imply. My downstream task did wait for all of its upstream tasks to finish, but when one of them failed, it failed everything downstream. Looking at the name of the trigger rule, that seems obvious that it implies none can fail, but just saying - that the `none_failed_or_skipped` does **not** serve the functionality of all parent/upstream tasks having finished executing, and at least one of them has succeeded. As soon as one of the upstream tasks fails, all of its downstream tasks fail. -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
