Start and inspect automation runs
The Runs tab shows real executions of an automation. Open a run to see the version it used, the path it followed, and the values recorded by its steps.
Automations is in Early access. Your workspace permissions determine which actions you can perform.
Early access run allowance
During early access, your organization receives 1,000 included runs per UTC calendar month, shared across its workspaces. The allowance resets at 00:00 UTC on the first day of the month. The Automations page shows your organization's usage and the reset time in your selected time zone.
A real run counts when it starts, including manual starts and runs started by events or schedules. It still counts if it later fails, is canceled, or is deleted. Workflow previews and step retries do not use additional runs. Duplicate events, filter misses, and starts skipped because of overlap settings do not use runs.
When you reach the allowance, new runs cannot start until the reset. Existing runs can finish, including waits and retries. You can continue editing and previewing workflows and viewing run history. Triggers skipped at the limit are not queued for the next month.
Unused runs do not carry over. Paid overage is unavailable during early access. Messaging channel charges still apply to messages sent by a workflow.
Start a run manually
- Open a published application-event automation and select Start run.
- Review the published trigger and supply its required data. Replace illustrative values with the values you intend the real workflow to use.
- Acknowledge that the run performs real actions, then select Start run.
- Open View runs and inspect the resulting execution.
The run uses the published version, including when the editor has newer draft changes. Actions can send messages, change records, and incur charges.
If the result is Run skipped, inspect the automation's overlap settings and active runs. A skipped start does not create a failed run.
If a submission loses its response, inspect Runs before starting another request. The first request may have started a run even though its confirmation did not arrive.
Understand run status
| Status | Meaning |
|---|---|
| Queued | Accepted and awaiting processing. |
| Running | Processing the workflow. This can include recovery between attempts. |
| Waiting | Paused at a delay or event wait. |
| Succeeded | Reached a successful ending, including a handled failure path. |
| Failed | Ended with an unhandled failure, deadline failure, or an explicit failed exit. |
| Canceled | Stopped through cancellation. Previously accepted external actions may still finish. |
Run success describes the workflow's ending. For message delivery, inspect the channel record or a delivery-wait result.
Inspect a run
- Open the automation's Runs tab and select a run.
- Review its status, starting time, version, and final outcome.
- Expand the steps to inspect Input, Result, and Error where recorded.
- Compare the recorded branch with the condition and data that selected it.
Use the field search to find a particular value. Turn off Hide null fields when you need to distinguish an explicit no-value field from a field you cannot see.
An Exit node can provide a final result and outcome reason. A deliberately failed exit can have a reason without a platform error. A cancellation event can supply its own cancellation reason.
Some sensitive values are omitted from retained detail, and expired detail cannot be recovered from aggregate metrics.
Cancel active work
Open the active run and select Cancel run. Review the confirmation and wait for the run's status to settle.
Cancellation stops further processing at a cancellation boundary. It cannot recall a message or undo a contact change already accepted by another service. Pausing the automation separately prevents new starts.
Next steps
- Read automation metrics.
- Troubleshoot an automation.
- Publish and manage automations.
- Browse the Automations guides.
Related resources
Continue with the documentation, guides and examples for this topic. Resources are in English.