Workflow runs

Every time a workflow's trigger fires, Reach records a run. The Runs page shows that history for one workflow so you can confirm it executed, see what record set it off, and read the error if a step failed. Open it from the View runs button on the workflow editor, or go straight to /workflows/[id]/runs. The page is read-only — there is nothing to configure here.

Reading the runs table

Runs are ordered newest first, and the page loads up to the 50 most recent. Each row has five columns:

• Status — the run's outcome as a colored badge. See the status reference below.
• Triggered by — the record that set the workflow off, shown as the record type followed by the first eight characters of its ID. When a run has no triggering record, this cell reads View steps instead. The cell is the link that opens the run's steps.
• Started — when the run began, as a short month/day and time.
• Duration — elapsed time from start to finish, formatted as 250ms, 1.5s, or 2m 30s. A run that has not finished shows a dash.
• Error — the run-level error message, if any (for example a condition that could not be parsed). The table truncates it to 80 characters; the full text appears when you open the run.

Run statuses

A run carries one of five statuses:

• Queued — accepted and waiting to run.
• Running — in progress.
• Completed — every step finished without error.
• Errored — a step failed and stopped the run.
• Cancelled — the run was stopped before completing.

Inspecting a run's steps

Click a row's Triggered by link to open a Run steps panel below the table. The selected run is also reflected in the URL as ?run=<id>. The panel header repeats the run's status badge and shows its short ID. If the run failed, its full error message appears in a highlighted box at the top of the panel.

Each step is one action from the workflow, listed in execution order with these columns:

• # — the step's position in the action chain, starting at 1.
• Action — the action that ran, in plain language (for example Set a field, Move to a lifecycle stage, or Call a webhook).
• Status — one of Queued, Running, Completed, Errored, or Skipped. Skipped means a condition check kept the step from running.
• Duration — how long the step took, in the same format as the run duration.
• Output / error — a failed step shows its error message (truncated to 100 characters); a successful step shows a short JSON summary of its result (truncated to 120 characters). Steps with no output, or an empty result, leave this cell blank.

If a run recorded no steps, the panel reads This run has no recorded steps.

When there are no runs

A workflow that has never fired shows an empty state titled No runs yet with the note that runs and their steps will appear once the trigger fires. If you expect runs and see none, confirm the workflow is active and that its trigger has actually occurred.

What the page does not do

There is no filtering or search on the Runs page. You see the 50 most recent runs for this workflow regardless of trigger type or outcome. The list is scoped to a single workflow, so a run from another workflow never appears here, and opening a run that belongs to a different workflow shows no steps panel.