Find failed runs and the records that failed

Updated 22 October 2026 · For developers

A common use of the API is a daily check that reports any run that didn't fully succeed, with the reason for each failed record.

Before you start

You need an API key. See Get started with the Run History API.

1
List the runs that need attention
Ask for failed and partly successful runs since your last check:
```
curl "https://{tenantname}.automatedon.io/api/v1/runs?status=Failed,PartiallySucceeded&from=2026-10-21&pageSize=200" \
  -H "X-Api-Key: $AO_API_KEY"
```
Add processId to check one process only. Dismissed runs are left out unless you add includeDismissed=true.
Check for a run-level error

If a run's errorMessage is set, the run itself failed, usually because its dataset couldn't be collected. There won't be any records to look at.
3
Get the failed records
For each run with a failedCount above 0, get its failed records with their steps:
```
curl "https://{tenantname}.automatedon.io/api/v1/runs/4182/records?status=Failed&include=steps" \
  -H "X-Api-Key: $AO_API_KEY"
```
Each record's errorMessage is its first error. In steps, look for actions where executed is true and success is false. Actions with executed false were skipped because an earlier action in the step failed.

Fix the cause in AutomatedOn, then requeue the run there if you need to. The API can't requeue or dismiss runs.