Following runs

Each time an active workflow fires, it gives a run: what ran, block by block, with its result.

Depending on your plan Automations › History, or the editor's Runs tab Every member sees runs; their data, restarting and cancelling: administrators and Automator author

In the editor

The editor's Runs tab: run #24 completed, its trigger, its revision, its dates and its duration, the Restart button, then its four successful steps with the output taken by the condition.

The Runs tab lists the workflow’s runs, which you can filter by status: Running, Completed, Failed, Canceled, Terminated, Timed out. Click one to see:

its trigger, the published revision that ran, its start, its end and its duration;
its steps: status, time, duration, Output taken by a condition, number of passes in a loop;
the error if there is one, with Highlight on the canvas to find the block at fault.

Show on canvas colours each block according to what it did during that run. Open leads to the run’s page.

A run’s page

Run #1 of Deal won → contract signed, waiting for approval: the five steps in a row, the Your approval is required message, the contract filled in by Atlas with its sources, the Edit, Reject and Send for signature buttons, then Cancel execution, History and Open editor. — Hover a number to find the area. Click the screenshot to enlarge it.

The steps are shown in a row, from left to right, with their state. The link at the top opens the record that started the run. Click a step to see its details; the Step data (input and output of each call) is only shown to administrators and to the workflow’s Automator author.

Giving your approval

When the run reaches a Your approval block, it waits. The designated person sees Your approval is required on this page and an alert in Today; the others see who is awaited.

For a contract filled in by Atlas, each value shows what it is based on. Edit corrects a value before sending.
Reject sends the flow through the Rejected or expired output.
The main button (here Send for signature) approves: the flow continues from Approved.

Only the designated person’s click decides: neither another member nor Atlas can approve in their place.

Restarting or cancelling

Restart starts a new run with the same inputs and the current published version. The workflow must be active. Actions already done (records updated, external calls) may happen again.
Cancel execution stops it at the current block. What has already been done is not undone.

The history

The run history: filters by automation and by status, then the runs with their status, trigger, start and duration, including a failed one with its error message. — Hover a number to find the area. Click the screenshot to enlarge it.

Automations › History gathers the runs of every workflow of the organization, most recent first. Filter by automation or by status; a failed run shows its error on the row. Click a row to open its page.

Run now

On an active workflow, Run now starts the published version right away. The actions are real: records updated, external services and AI called. Publish your changes first: only the published version runs.

With a scheduled trigger, the workflow starts as it would at a due time.
With a CRM event, you write the simulated event in JSON (64 KB at most); replace the sample id with a real record’s if blocks update it.
With a manual launch tied to an object, you choose the record passed in.