This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new 821e15c199 Update faq.rst (#30343)
821e15c199 is described below
commit 821e15c1995f0067c95ee90394d11f022d66fe39
Author: Dris101 <[email protected]>
AuthorDate: Wed Mar 29 13:03:01 2023 +0100
Update faq.rst (#30343)
Update FAQ to reflect that depends_on_past and wait_for_downstream treat
SKIPPED and SUCCESS the same.
---
docs/apache-airflow/faq.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/apache-airflow/faq.rst b/docs/apache-airflow/faq.rst
index 825206ad5b..bbffd4b333 100644
--- a/docs/apache-airflow/faq.rst
+++ b/docs/apache-airflow/faq.rst
@@ -57,10 +57,10 @@ There are very many reasons why your task might not be
getting scheduled. Here a
- Are the dependencies for the task met? The task instances directly
upstream from the task need to be in a ``success`` state. Also,
if you have set ``depends_on_past=True``, the previous task instance
- needs to have succeeded (except if it is the first run for that task).
+ needs to have succeeded or been skipped (except if it is the first run for
that task).
Also, if ``wait_for_downstream=True``, make sure you understand
what it means - all tasks *immediately* downstream of the *previous*
- task instance must have succeeded.
+ task instance must have succeeded or been skipped.
You can view how these properties are set from the ``Task Instance Details``
page for your task.
