Skip to main content

Viewing executions

When you open an execution, the flow editor switches into a read-only mode and becomes a live status view instead of an authoring surface. Use it to see exactly how a flow ran — which steps succeeded, which failed, and where execution is at right now.

What read-only mode changes​

Read-only mode hides every authoring affordance:

  • No + buttons on connections or at the end of sequences — you cannot add steps into a running flow.
  • No × remove buttons — steps cannot be taken out mid-execution.
  • Blocks cannot be dragged around.
  • The ghost placeholder for empty branches is not shown.

Everything else works the same: zoom, pan, fit view, and minimap toggle — see Overview for the shared canvas controls.

Clicking a step in read-only mode opens the execution logs for just that step, so you can investigate what happened without scrolling through the full execution log.

Status badges​

Each step shows small status icons in its top-right corner that summarise what happened during this execution:

  • A success icon with a count for every time the step completed successfully.
  • An error icon with a count for every time the step failed.
  • A pending icon for steps that are queued but not yet started.
  • A running icon for the step that is currently executing.

Steps can carry more than one badge — a step inside a loop, for example, might show several successes and one error once the loop has run a few times.

Live refresh​

While an execution is in an active state, the editor polls for updates automatically so you do not have to reload the page manually:

  • Running — refreshes every second. You see each step change from pending to running to success as the job progresses.
  • Pending — refreshes every three seconds. The job is queued but has not started; a slower poll is enough because no step-level progress is happening yet.
  • Success / Error / other terminal states — no polling. The execution is done; further refreshes would be wasted round-trips.

The refresh is smart about how much of the page it re-renders:

  • If the overall execution status has not changed (for example, it was Running a second ago and is still Running now), only the step badges are refreshed. The rest of the page stays put.
  • If the overall status has changed (Running → Success, say), the whole page is re-rendered so the header fields reflect the new state. Your zoom and pan position are preserved either way.