Skip to content
Kanri

Run History

Every time a workflow’s trigger fires, Kanri creates a run. The Run History page shows all runs for a workflow — what triggered them, which record they’re for, what step they’re on, and whether they succeeded.

Viewing run history for a workflow

Section titled “Viewing run history for a workflow”
  1. Open any workflow in the editor.
  2. Click Runs in the toolbar.

The Runs page shows a list of all runs, most recent first. You can filter by status (Running, Done, Failed, Cancelled, etc.).

Each row shows:

  • The record the run is for (e.g., member name or invoice number), if applicable
  • The run status
  • What triggered the run (event, schedule, or manual)
  • When the run started
  • When it finished (if complete)
  • The workflow version it’s using

Run statuses

Section titled “Run statuses”

A Done message step is not proof of recipient delivery. Sending and delivery are separate background work; use the Outbox to check failures or suppression.

StatusWhat it means
RunningThe run is actively executing, or waiting inside a Delay step
WaitingThe run is paused while child runs from For Each or a Match all Switch complete
DoneThe run completed all steps successfully
FailedA step encountered an error the run couldn’t recover from
CancelledThe run was cancelled — see below

When does a run get cancelled?

Section titled “When does a run get cancelled?”

A run is cancelled when:

  • A Delay step’s Recheck trigger setting is on and the record no longer matches the original condition or recurring-schedule filter. See the Condition Stops Being True limitation.
  • The workflow has an exit condition set, and the run’s record matches it. Unlike the re-check above, this is evaluated before every step, not just after a delay.
  • You disable the workflow, which also cancels in-progress runs.
  • The workflow is deleted.

Viewing a run’s details

Section titled “Viewing a run’s details”

Click any run in the list to open the run detail view. This shows:

  • The record the run is for
  • The current (or last completed) step
  • A step-by-step trace of everything that happened: which steps ran, what they did, and their results
  • Any error details if a step failed
  • The workflow version number (with a link to view that version in the canvas)

The step trace is particularly useful for debugging — you can see exactly what data each action received and what it returned.

While a run is active, the detail view refreshes automatically. If it is waiting at a Delay step, click Skip delay to continue without waiting. Later workflow actions still run.

To start a test, click Test Run from the builder or run history, choose the record (for Membership and Subscription workflows, choose a Member first), and start the run. Test runs use the published version and perform real actions: messages send and data changes apply. Use test records.

Viewing all runs across all workflows

Section titled “Viewing all runs across all workflows”

Go to Workflows in the sidebar and click All Runs (top right of the Workflows list page). This shows every run across every workflow, not just one.

You can filter by status to quickly find failing runs that need attention.

Debugging a failed run

Section titled “Debugging a failed run”

If a run shows a Failed status:

  1. Click the run to open its detail view.
  2. Look at the step trace. Find the step marked as failed.
  3. Check the error details — it will usually say what went wrong (for example, “member has no email address”, “invalid template ID”, or “required field is missing”).
  4. Fix the underlying issue (update the member’s record, fix the template, or adjust the workflow).
  5. A step’s queued task can be attempted up to five times before the run is marked Failed. A run already marked Failed does not automatically restart after you fix the problem. Starting a new manual run starts the workflow again, including earlier steps, so check for messages or changes already completed before repeating it.

Common failure causes:

  • A required field (like an email address) is missing on the record.
  • A template referenced in a step was deleted.
  • A record referenced in a step no longer exists.
  • An action’s required parameters weren’t filled in correctly.

What happens to runs when you publish a new version

Section titled “What happens to runs when you publish a new version”

Runs that started before a new publish keep running on the version they started with. Publishing a new version only affects new runs created after the publish. See Version History for more details.

Next steps

Section titled “Next steps”