How-toRecipes for one specific task, for when you know the basics and have a goal.

Debugging workflows using interactive mode

When a workflow runs, you can open that specific run in interactive mode to see exactly what happened, job by job.

This guide shows how to use interactive mode to inspect and debug a workflow run. It builds on the first step of Troubleshooting your workflow, which covers finding the run to open.

Opening a run in interactive mode

Open Workflow Starts (under View) and click a start in the history list to open it. This opens the run in interactive mode.

Following the timeline

Interactive mode shows the exact execution path the workflow has taken using the timeline:

  • A job that has run is shown as opaque.
  • A job that has not run yet is shown as slightly transparent.
  • A job with a red icon indicates a runtime error.

This lets you follow the flow step by step and see exactly where execution stopped or went wrong.

Inspecting a job

Click a job on the timeline to inspect what it did and which decisions it made, for example which condition path it took or what data it read or wrote in the workflow context.

Moving the debug pointer

Interactive mode also lets you move the debug pointer to a specific point in the flow. This allows you to:

  • Debug an individual job in isolation.
  • Rerun part of the flow from that point, without having to trigger the entire workflow again.

This is especially useful while building a new workflow, or when narrowing down where in a longer flow a problem occurs.