Testing and run history

The editor has a built-in test mode that walks your whole automation against real data without touching anything. No records are changed and no messages or emails go out, so you can test as many times as you like, even on a draft.

1. Open the automation in the editor.
2. Open the Debug tab in the drawer on the left.
3. Pick a sample record to run against if you want a specific one.
4. Click Run test.

The execution timeline shows each step with its own status. If items inside a loop fail, they are summarized inline so you can spot the pattern.

A test run never sends anything. When you want a published automation to run immediately with real effects, use Run now from the Automations table.

1. Go to Automations and find the automation's row.
2. Click the play button to open the Run now popover.
3. Pick a target record if the automation needs one.
4. Click Run now. The published automation runs with real effects.

The Runs tab on the Automations page lists every individual run across all of your automations. Filter the list by status with the status dropdown. Click an automation's name to open the editor with that run shown on the canvas.

Each run shows one of six statuses: Running, Completed, Completed with errors, Failed, Skipped, or Cancelled.

Every run records an execution timeline: what each step did, its status, and the reason when a step was skipped. An email step that hits the daily cap, for example, is recorded as skipped with a note that the cap was reached, and the run itself carries on.

Click an automation's name in the Runs tab or under recent failures and the editor opens with that run on the canvas. Each step shows whether it succeeded, failed, or was skipped. A failed step shows its error at the bottom of its card. A step that succeeded shows how long it took and how many records it processed, and a loop shows how many items succeeded and failed. If a step also has a setup problem, its card shows that warning instead.

Click a step to see its Last run details at the top of the settings panel: status, duration, records processed, and the error if it failed. View in debug panel opens that step in the Debug tab so you can read its input and output.

A note at the top of the canvas shows when the run started. If the automation changed after that run, the note says some steps may not match what ran. Close the note, start a new test, or edit anything to go back to the plain editor.