From 80151b4249939101b55b39c2a5e55bc8f59a7842 Mon Sep 17 00:00:00 2001 From: James Frost Date: Fri, 25 Sep 2026 13:48:59 +0100 Subject: [PATCH 1/2] Indicate that [[[outputs]]] are a third-level setting Fixes #970 --- src/tutorial/furthertopics/message-triggers.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/tutorial/furthertopics/message-triggers.rst b/src/tutorial/furthertopics/message-triggers.rst index 19e16b2576c..7ab62fa2f8f 100644 --- a/src/tutorial/furthertopics/message-triggers.rst +++ b/src/tutorial/furthertopics/message-triggers.rst @@ -41,8 +41,8 @@ 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][]`` 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 From dc1795cb11e2fb81c2353c24bea2f3935a0b1d60 Mon Sep 17 00:00:00 2001 From: James Frost Date: Fri, 25 Sep 2026 13:51:45 +0100 Subject: [PATCH 2/2] Fix indentation of bullets in message triggers tutorial This was breaking the list formatting as the indented section was treated as a separate block. --- src/tutorial/furthertopics/message-triggers.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/tutorial/furthertopics/message-triggers.rst b/src/tutorial/furthertopics/message-triggers.rst index 7ab62fa2f8f..646a0d8cf6c 100644 --- a/src/tutorial/furthertopics/message-triggers.rst +++ b/src/tutorial/furthertopics/message-triggers.rst @@ -42,12 +42,12 @@ 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, + ``[runtime][]`` 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.