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 639210a7e0 Update SLA wording to reflect it is relative to Dag Run
start. (#27111)
639210a7e0 is described below
commit 639210a7e0bfc3f04f28c7d7278292d2cae7234b
Author: Damian Shaw <[email protected]>
AuthorDate: Thu Oct 27 10:34:57 2022 -0400
Update SLA wording to reflect it is relative to Dag Run start. (#27111)
---
docs/apache-airflow/concepts/tasks.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/apache-airflow/concepts/tasks.rst
b/docs/apache-airflow/concepts/tasks.rst
index 63fbe818e0..c3f9d1de3b 100644
--- a/docs/apache-airflow/concepts/tasks.rst
+++ b/docs/apache-airflow/concepts/tasks.rst
@@ -158,7 +158,7 @@ If you merely want to be notified if a task runs over but
still let it run to co
SLAs
----
-An SLA, or a Service Level Agreement, is an expectation for the maximum time a
Task should take. If a task takes longer than this to run, it is then visible
in the "SLA Misses" part of the user interface, as well as going out in an
email of all tasks that missed their SLA.
+An SLA, or a Service Level Agreement, is an expectation for the maximum time a
Task should be completed relative to the Dag Run start time. If a task takes
longer than this to run, it is then visible in the "SLA Misses" part of the
user interface, as well as going out in an email of all tasks that missed their
SLA.
Tasks over their SLA are not cancelled, though - they are allowed to run to
completion. If you want to cancel a task after a certain runtime is reached,
you want :ref:`concepts:timeouts` instead.
