From b2d6d07a974db6e48686c83018d72552787801af Mon Sep 17 00:00:00 2001 From: Haytham AbuelFutuh Date: Thu, 25 Jun 2020 11:09:44 -0700 Subject: [PATCH 1/2] Fix on failure policy docs --- rsts/user/features/on_failure_policy.rst | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/rsts/user/features/on_failure_policy.rst b/rsts/user/features/on_failure_policy.rst index 0fa3ca5faa..326d4680cd 100644 --- a/rsts/user/features/on_failure_policy.rst +++ b/rsts/user/features/on_failure_policy.rst @@ -1,7 +1,10 @@ .. _on-failuire-policy: +On Failure Policy +################# + What is it -========== +---------- The default behavior for when a node fails in a workflow is to immediately abort the entire workflow. The reasoning behind this thinking is to avoid wasting resources since the workflow will end up failing anyway. There are certain cases however, when it's desired for the From a193b8662cdc5e9d040f07051356dde0b7f3b76b Mon Sep 17 00:00:00 2001 From: Haytham AbuelFutuh Date: Thu, 25 Jun 2020 11:48:31 -0700 Subject: [PATCH 2/2] Update rsts/user/features/on_failure_policy.rst Co-authored-by: Yee Hing Tong --- rsts/user/features/on_failure_policy.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rsts/user/features/on_failure_policy.rst b/rsts/user/features/on_failure_policy.rst index 326d4680cd..e4d164c9f7 100644 --- a/rsts/user/features/on_failure_policy.rst +++ b/rsts/user/features/on_failure_policy.rst @@ -1,4 +1,4 @@ -.. _on-failuire-policy: +.. _on-failure-policy: On Failure Policy #################