Troubleshooting: Notes on Jinja2 and Startup config logs

src/user-guide/troubleshooting.rst

@@ -61,6 +61,28 @@ for debugging some specific issues:
    These files can allow you to see how the configuration was changed between
    restarts and reloads.
 
+   Each time a workflow is
+
+   * Played for the first time
+   * Played from stopped
+   * Reloaded
+
+   the configuration used is recorded in a file in ``log/config``.
+   This provides a series of snapshots of the configuration.
+   These files are named:
+
+   ``<LOG FILE NUMBER>-<EVENT>-<RESTART NUMBER>``.
+
+   If for example we did:
+
+   .. code-block:: console
+
+      # Command            # File created
+      cylc play workflow   # 01-start-01.cylc
+      cylc vr workflow     # 02-reload-01.cylc
+      cylc stop workflow
+      cylc play workflow   # 03-restart-02.cylc
+
 
 Shell Login/Profile Files
 -------------------------
@@ -219,7 +241,7 @@ To find out more, see the ``job.err`` file.
 .. note::
 
    To ensure Cylc jobs fail when they are supposed to, Cylc configures Bash
-   to be a bit stricter than it is by default by running ``set -euo pipefail``.
+   to be stricter than it is by default by running ``set -euo pipefail``.
 
    .. cylc-scope:: flow.cylc[runtime][<namespace>]
 
@@ -229,6 +251,11 @@ To find out more, see the ``job.err`` file.
 
    .. cylc-scope::
 
+.. note::
+
+   One particularly common issue when developing a workflow is failure
+   to make a script executable. Use ``ls -l`` to check.
+
 If you're struggling to track down the error, you might want to put the
 workflow into debug mode::
 
@@ -470,6 +497,97 @@ environments. If you encounter this issue in combination with containers,
 please let us know.
 
 
+Debugging Workflow Configurations
+---------------------------------
+
+Cylc Debugging Utilites
+^^^^^^^^^^^^^^^^^^^^^^^
+
+.. TODO Add cheatsheet link here
+
+Cylc comes with a number of utilies designed to allow inspection of
+workflows:
+
+``cylc view``
+   Prints workflow configurations before full parsing by Cylc. This
+   can include :ref:`Jinja2 <troubleshooting.jinja2>` (use ``-j``)
+   or Empy template processing.
+
+   Include files can be inlined (use ``-i``).
+
+``cylc config``
+   Prints workflow configuration after Cylc has parsed the runtime
+   configuration. For example:
+
+   .. code-block:: cylc
+
+      [runtime]
+          [[foo, bar]]
+              script = echo 'Hello'
+          [[bar]]
+              post-script = echo 'World'
+
+   would be shown as:
+
+   .. code-block:: cylc
+
+      [runtime]
+          [[root]]
+          [[foo]]
+              script = echo 'Hello'
+          [[bar]]
+              script = echo 'Hello'
+              post-script = echo 'World'
+
+``cylc lint``
+   #. Checks the config against the :ref:`style_guide`.
+   #. Looks deprecated Cylc 7 configurations and recommends
+      Cylc 8 configurations to replace them.
+
+   .. seealso::
+
+      :ref:`cylc_lint_script`
+
+``cylc validate``
+
+   Validate a workflow configuration.
+
+   .. seealso::
+
+      :ref:`Validation`
+
+.. _troubleshooting.jinja2:
+
+See what the Jinja2 is doing
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Sometimes understanding what Jinja2 templating is doing
+to a workflow configuration can be difficult.
+
+``cylc view --process`` (or ``-p``) shows you what the
+configuration will look like after Jinja2 processing.
+
+For example:
+
+.. code-block:: jinja2
+
+   {% for n in my_function(3) %}
+       R/1983/P{{n}}Y = cicada_{{n}}[-P{{n}}Y] => cicada_{{n}}
+   {% endfor %}
+
+is much easier to understand as:
+
+.. code-block:: cylc-graph
+
+      R/1983/P2Y = cicada_2[-P2Y] => cicada_2
+      R/1983/P3Y = cicada_3[-P3Y] => cicada_3
+      R/1983/P5Y = cicada_5[-P5Y] => cicada_5
+
+If you have installed and played a workflow
+(even using ``play --pause``) this processed content
+is shown in ``log/config/flow-processed.cylc``.
+
+
 Getting Help
 ------------
 

src/workflow-design-guide/style-guide.rst

@@ -1,3 +1,5 @@
+.. _style_guide:
+
 Style Guidelines
 ================