Skip to content

Commit

Permalink
Explain first intervention example.
Browse files Browse the repository at this point in the history
  • Loading branch information
hjoliver committed Aug 15, 2024
1 parent 9e5c8f0 commit ae73a81
Showing 1 changed file with 15 additions and 2 deletions.
17 changes: 15 additions & 2 deletions src/user-guide/interventions/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -5,8 +5,8 @@ Interventions

Sometimes things don't go to plan!

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

This section of the documentation covers some of the common interventions you
Expand Down Expand Up @@ -87,6 +87,19 @@ Re-Run a Task
$ cylc trigger <workflow>//<task>
.. tab-item:: Explanation
:sync: explanation

In this example, a failed task blocked the flow because downstream
tasks depended on its success. Triggering the failed task to run again
allows (if it succeeds this time) the original flow to continue.

Activity will only continue downstream of a triggered task if the
flow has not already traversed that part of the graph.

So triggering a succeeded task, for example, will typically only cause
the task itself to run, unless you told Cylc to trigger a new flow.


Re-Run Multiple Tasks
---------------------
Expand Down

0 comments on commit ae73a81

Please sign in to comment.