Skip to content

Indicate that [[[outputs]]] are a third-level setting and fix indentation of bullets in message triggers tutorial #971

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jfrost-mo merged 2 commits into from
Sep 28, 2026
Merged

Indicate that [[[outputs]]] are a third-level setting and fix indentation of bullets in message triggers tutorial #971

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
80151b4
Indicate that [[[outputs]]] are a third-level setting
jfrost-mo Sep 25, 2026
dc1795c
Fix indentation of bullets in message triggers tutorial
jfrost-mo Sep 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions src/tutorial/furthertopics/message-triggers.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,13 +41,13 @@ How to create a message trigger

In order to get our workflow to trigger messages, we need to:

* specify our custom message in a section called ``[[outputs]]`` within the
``[runtime]`` section of our workflow,
* specify our custom message in a section called ``[[[outputs]]]`` within the
``[runtime][<namespace>]`` section of our workflow,

* add ``cylc message -- "${CYLC_WORKFLOW_ID}" "${CYLC_TASK_JOB}" "YOUR CHOSEN TRIGGER MESSAGE"``
to the ``script`` section of ``[runtime]``, your chosen trigger message
should be unique and should exactly match the message defined in
``[[outputs]]``.
to the ``script`` section of ``[runtime]``, your chosen trigger message
should be unique and should exactly match the message defined in
``[[outputs]]``.

* Refer to these messages in the ``[dependencies]`` section of our workflow.

Expand Down
Loading