From eb10fd808596d96c9763e4b90fe0d1802f02cc03 Mon Sep 17 00:00:00 2001 From: "sg-doc-holiday[bot]" <219201796+sg-doc-holiday[bot]@users.noreply.github.com> Date: Thu, 22 Jan 2026 10:18:06 +0000 Subject: [PATCH 1/2] workflow-management: update investigate-workflow-run.mdx Document the existing Runs list action labels ('Rerun on latest version' / 'Retry on latest version') and the observed behavior that the action retries using the latest locked workflow version, matching the UI labels and server retry implementation. --- workflow-management/investigate-workflow-run.mdx | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/workflow-management/investigate-workflow-run.mdx b/workflow-management/investigate-workflow-run.mdx index 959b112..fef2c51 100644 --- a/workflow-management/investigate-workflow-run.mdx +++ b/workflow-management/investigate-workflow-run.mdx @@ -34,6 +34,15 @@ In the **Recent Runs** pane that opens on the left, click a run that you want to This will open the selected run in the **Run Details** pane. +## Retrying a run on the latest version + +From the **Runs** list, use the run actions menu (three dots) to retry a run. + +* For successful runs, the action is labeled **Rerun on latest version**. +* For failed or stopped runs, the action is labeled **Retry on latest version**. + +When you select this action, OpenOps retries the run using the latest locked version of the workflow. + ## Investigating in the Run Details view In the **Run Details** pane, each workflow step will display a ✅ or a ❌ to indicate its execution status. From 719e48b48e2628f26e84b734e2f266235fe2d732 Mon Sep 17 00:00:00 2001 From: "sg-doc-holiday[bot]" <219201796+sg-doc-holiday[bot]@users.noreply.github.com> Date: Thu, 22 Jan 2026 10:19:17 +0000 Subject: [PATCH 2/2] workflow-management: update investigate-workflow-run.mdx Update rerun/retry description to match current behavior where selecting rerun/retry on latest version starts a new run using the latest locked workflow version. --- .../investigate-workflow-run.mdx | 55 ++++++++++++++++++- 1 file changed, 54 insertions(+), 1 deletion(-) diff --git a/workflow-management/investigate-workflow-run.mdx b/workflow-management/investigate-workflow-run.mdx index fef2c51..a22529a 100644 --- a/workflow-management/investigate-workflow-run.mdx +++ b/workflow-management/investigate-workflow-run.mdx @@ -34,6 +34,42 @@ In the **Recent Runs** pane that opens on the left, click a run that you want to This will open the selected run in the **Run Details** pane. +--- +title: 'Investigating Workflow Runs' +description: 'How to troubleshoot and debug workflow runs' +icon: 'magnifying-glass' +--- + +import { NarrowImage } from '/snippets/narrow-image.jsx' +import RestartContainers from '/snippets/restart-containers.mdx' + +If a workflow didn't execute the way you expected it to, you can investigate what went wrong by viewing the history of workflow runs. You can do this [from the **Runs** view](#finding-a-run-from-the-runs-view) or directly [from the workflow editor](#finding-a-run-from-the-workflow-editor). + +## Finding a run from the Runs view + +Click **Runs** in the OpenOps main menu. + +This opens the list of all runs across all your workflows, with the most recent runs shown first: +![The list of all workflow runs](/images/runs-default.png) + +You can filter the list by workflow name, run status (succeeded, failed, paused, timeout, etc.), type (triggered, manual run, test run), or a date range: +![Workflow runs with filters applied](/images/runs-filters.png) + +When you've found a run you want to investigate, click on it. This will open the workflow editor in a view-only mode. + +Alternatively, if a run is taking longer than expected or is stuck in a paused state, you can abort it by clicking the three-dot menu on the right and selecting **Stop Run**: +![Stopping a run](/images/runs-stop.png) + +## Finding a run from the workflow editor + +If the workflow you want to investigate is already open in the workflow editor, click **Run logs** in the top menu: + + +In the **Recent Runs** pane that opens on the left, click a run that you want to investigate. Failed runs are marked with the ❌ icon: + + +This will open the selected run in the **Run Details** pane. + ## Retrying a run on the latest version From the **Runs** list, use the run actions menu (three dots) to retry a run. @@ -41,7 +77,24 @@ From the **Runs** list, use the run actions menu (three dots) to retry a run. * For successful runs, the action is labeled **Rerun on latest version**. * For failed or stopped runs, the action is labeled **Retry on latest version**. -When you select this action, OpenOps retries the run using the latest locked version of the workflow. +When you select this action, OpenOps starts a new run using the latest locked version of the workflow. + +## Investigating in the Run Details view + +In the **Run Details** pane, each workflow step will display a ✅ or a ❌ to indicate its execution status. + +Click on a failed step to see its inputs and outputs. Explore the outputs to view the error message: + + +To update the workflow to address the error, click **Edit** in the top-right corner of the workflow editor. This switches the editor from view-only mode, enabling you to select the problematic step and modify its properties. + +## Changing the default timeout + +By default, OpenOps times out if a workflow runs for more than 10 minutes. This applies to both scheduled runs and test runs. + +If you build long-running workflows, you may want to extend the default timeout. To do this, open the `.env` file in your OpenOps installation directory and add a new environment variable named `OPS_FLOW_TIMEOUT_SECONDS`. Set its value to the desired timeout in seconds — for example, `900` for 15 minutes or `3600` for 1 hour. + + ## Investigating in the Run Details view