Folder
Runs and Monitoring
Runs and Monitoring covers how workflows execute, how to follow their progress, and how to investigate or stop an execution. Use these tools to validate drafts in the Designer and to operate published workflows after they begin receiving live traffic.
Run lifecycle
A run starts from one trigger and creates a sequence of block execution instances. Each instance reports its own state, cost, and runtime messages, while the run header summarizes the complete execution.
The main run states are:
| State | Meaning |
|---|---|
running | At least one block is still executing or waiting. |
success | The run reached a successful terminal state. |
failed | A block error prevented the run from completing normally. |
cancelled | A user stopped the run before all downstream work completed. |
Block states can change before the run summary refreshes. Read the execution list together with the run-level status, start and finish times, and cost.
Start here
- Test Runs in the Designer explains how to start a saved draft from a selected trigger, read live block states, inspect logs, and cancel a test.
- Run Published Workflows explains how live triggers use the published version, how to correlate and inspect production runs, and why later draft changes stay isolated.
- Browse Run History explains global, project, and pipeline scopes; status filters; pagination; automatic refresh; and navigation into run details.
- Read Block Logs and Output explains execution instances, structured logs, rendered output, timing, cost, and safe diagnostic practices.
- Cancel a Running Workflow explains dashboard, alerts-popover, and run-detail cancellation; terminal state confirmation; and the limits of stopping work already in progress.
- Alerts and User Events explains unread notifications, alert navigation and acknowledgement, dashboard activity, browser-localized timestamps, and the 30-day user-event log.
Explore this folder
Test Runs in the DesignerUse a test run to execute a saved workflow version from the Designer before publishing it.Run Published WorkflowsUnderstand how live triggers start isolated runs against the currently published workflow version rather than later draft changes.Browse Run HistoryFilter Builders run history by scope and status, then inspect execution timing, cost, block paths, logs, output, and errors.Read Block Logs and OutputThe run inspector shows which blocks executed, what each execution reported, and how much it contributed to the run's cost.Cancel a Running WorkflowCancel an active run from the dashboard, alerts, or run inspector to prevent it from starting additional workflow work.Alerts and User EventsUse Alerts to identify operational conditions requiring action and Events to audit user changes across Builders resources.
