Triage Workflow Runs
Use the workflow runs list to find failed, queued, running, and unexpected workflow executions.
The workflow runs list shows recent executions for one workflow. Use it to find failures, confirm new versions are working, and spot unexpected activity before users report the issue.
Open The Runs List
- Open Workflows.
- Open the workflow.
- Select Runs.
- Review status, trigger type, start time, error summary, and pagination.
Select a run to open the full step log and context.
Read Statuses
Use statuses to prioritize review:
- failed: open immediately and inspect the first failed step;
- running: check duration and whether it is still making progress;
- queued: confirm workers and trigger volume if it stays queued;
- succeeded: spot-check after publishing or changing integrations;
- cancelled: confirm who cancelled it and what had already completed.
The list view helps you choose which run to inspect first. The run detail page is where you prove what happened.
Triage After Publishing
After publishing a workflow, review the next few runs from the list. Confirm the trigger type is expected, statuses are healthy, and no repeated failures or duplicate runs appear.
For customer-facing workflows, open at least one successful run and verify the created message, task, invoice, ticket, or record.
Investigate Repeated Failures
If several runs fail with the same error, pause or narrow the workflow before retrying. Repeated failures can create duplicate tasks, customer messages, provider calls, or noisy support work.
Collect the workflow name, run IDs, trigger type, first failed step, error text, and affected records before changing the workflow.
Handle Empty Runs
If the list is empty, confirm the workflow is published, enabled, and has a trigger that can actually fire. For manual workflows, run a manual test. For webhook workflows, confirm the external system is sending events to the current endpoint.