Check run history and fix a failed automation

Every time an automation runs, the run is recorded with its status and the result of each step. Use run history to confirm an automation is working and to find out why one failed.

See the runs for one automation

Open the automation. The Run History panel lists its runs, newest first. Filter by All, Success, Failed or Running. Click a run to expand it and see:

Started and Duration.
Trigger: what started the run.
Run ID: a short reference you can quote to support.
Steps: each step with a passed, failed or skipped mark and its message.

Selecting a run also marks the steps on the flow map, so you can see how far it got.

See runs across all automations

On the Automations page, open the Runs tab. It shows how many runs succeeded, the success rate, a chart of the last 14 days and a list of recent runs. Click a run to jump to its automation.

Run statuses

Success: every step completed.
Partial: the run finished, but at least one step did not complete.
Failed: the run stopped on an error.
Running: still in progress. A running run has a stop button if you need to cancel it.
Cancelled: the run was stopped.

Fix a failed run

Open the failed run and find the step with the red X. Its error message is shown under the step name.
Hover the failed step and click Fix. The assistant opens with the automation name, the step and the error already filled in.
Let the assistant correct the step.
Run a dry run to confirm the fix, then run the automation for real.

Common causes

A connected app needs reconnecting. If the step uses a connected app, open Tools, choose Integrations and look for a connection marked Expired. Click Reconnect.
A field was renamed or removed. A step that refers to a field that no longer exists fails. Ask the assistant to update the step.
A credential is missing. A step that calls an outside service needs its key saved under Credentials on the Automations page.
You are out of AI credits. Steps that use AI are refused when your workspace has no AI credits left.
Your workspace is out of run credits. See Run credits and AI credits for automations.

If it still fails

Copy the Run ID and the error message and send them to support. Those two things are what support needs to find the run.