From 30bfb9c404a056a72d759aa27d8011faad9eb8cb Mon Sep 17 00:00:00 2001 From: Oliver Sanders Date: Mon, 15 Apr 2024 16:45:10 +0100 Subject: [PATCH] docs: submit-failed must be optional --- src/user-guide/writing-workflows/scheduling.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/user-guide/writing-workflows/scheduling.rst b/src/user-guide/writing-workflows/scheduling.rst index d56852f69a..fbf8e2bd7f 100644 --- a/src/user-guide/writing-workflows/scheduling.rst +++ b/src/user-guide/writing-workflows/scheduling.rst @@ -1099,10 +1099,10 @@ To trigger off of a task submitting, or failing to submit: .. code-block:: cylc # B triggers if A submits successfully: - R1 = "A:submit => B" + R1 = "A:submit? => B" # D triggers if C fails to submit successfully: - R1 = "C:submit-fail => D" + R1 = "C:submit-fail? => D" A possible use case for submit-fail triggering: if a task fails to submit, possibly after multiple retries, another task that inherits (mostly) the same