@@ -441,53 +441,53 @@ but specify the "failed" output rather than
441
441
"succeeded".
442
442
443
443
444
- Hold The Workflow And Trigger Tasks One By One
445
- ----------------------------------------------
444
+ Pause The Workflow And Trigger Tasks One By One
445
+ -----------------------------------------------
446
446
447
447
:Example:
448
- I want to hold back the workflow while I manually run one or more tasks
448
+ I want to pause the workflow while I manually run one or more tasks
449
449
to fix a problem or test a task.
450
450
451
451
:Solution:
452
- * Hold all tasks after a specified cycle .
452
+ * Pause the workflow .
453
453
* Trigger the task(s) you want to run.
454
- * When you're done triggering, release the held tasks to allow the workflow
455
- to continue.
454
+ * When you're done triggering, resume (unpause) the workflow.
456
455
457
456
.. tab-set ::
458
457
459
458
.. tab-item :: GUI
460
459
:sync: gui
461
460
462
- .. image :: set-and-release-hold-point .gif
461
+ .. image :: trigger-while-paused .gif
463
462
:width: 75%
464
463
465
464
.. tab-item :: CLI
466
465
:sync: cli
467
466
468
467
.. code-block :: console
469
468
470
- $ # hold all tasks after the cycle "2000"
471
- $ cylc hold --after=2000 <workflow>
469
+ $ # pause the workflow
470
+ $ cylc pause <workflow>
472
471
473
472
$ # trigger the task(s) you want to run
474
- $ cylc trigger <workflow>//<cycle>/<task>
473
+ $ cylc trigger --now <workflow>//<cycle>/<task>
475
474
476
- $ # release the "hold point" to allow the workflow to continue
477
- $ cylc release --all <workflow>
475
+ $ # resume (unpause) the workflow to continue
476
+ $ cylc play <workflow>
478
477
479
478
.. note ::
480
479
481
480
The difference between the workflow "paused" state and the task "held" state:
482
481
483
482
Workflow Pause
484
- When a workflow is :term: `paused <pause> `, no new jobs will be submitted.
485
- This gives you an opportunity to make changes to the workflow, however, if
486
- you trigger tasks, they will not run until the workflow is resumed .
483
+ When a workflow is :term: `paused <pause> ` new jobs will not be submitted
484
+ automatically, but you can still trigger tasks manually.
485
+ This gives you an opportunity to make changes to the workflow.
487
486
488
487
Task Hold
489
488
When a task is :term: `held <hold> `, then it will not submit (if ready to
490
- submit) until released.
489
+ submit) until released. If you hold a running task its job will not be
490
+ affected, but it will not submit any :term: `retries <retry> ` until released.
491
491
492
492
493
493
I want to Skip a cycle of tasks and allow the workflow to continue
0 commit comments