Skip to content

Commit e5ba03f

Browse files
committed
Explain first intervention example.
1 parent 9e5c8f0 commit e5ba03f

File tree

1 file changed

+15
-2
lines changed

1 file changed

+15
-2
lines changed

src/user-guide/interventions/index.rst

Lines changed: 15 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,8 +5,8 @@ Interventions
55

66
Sometimes things don't go to plan!
77

8-
So Cylc allows you to take manual control of your workflow whilst it's running
9-
allowing you to do things like edit a task's configuration, re-run a section
8+
So Cylc allows you to take manual control of your workflow whilst it's running,
9+
to do things like edit a task's configuration, re-run a section
1010
of your graph or override task outputs.
1111

1212
This section of the documentation covers some of the common interventions you
@@ -87,6 +87,19 @@ Re-Run a Task
8787
8888
$ cylc trigger <workflow>//<task>
8989
90+
.. tab-item:: Explanation
91+
:sync: explanation
92+
93+
In this example, a failed task blocked the flow because downstream
94+
tasks depended on its success. Triggering the failed task to run again
95+
allows (if it succeeds this time) the original flow to continue.
96+
97+
The flow will only continue downstream of a triggered task if it has not
98+
already traversed that part of the graph.
99+
100+
So if you trigger a succeeded task that did not block the flow, only the
101+
triggered task itself will run unless you tell Cylc to start a new flow.
102+
90103

91104
Re-Run Multiple Tasks
92105
---------------------

0 commit comments

Comments
 (0)