Run History API: errors
Errors return a JSON body in the RFC 9457 problem details format.
{
"type": "https://tools.ietf.org/html/rfc9110#section-15.5.1",
"title": "Bad Request",
"status": 400,
"detail": "Unknown status 'Done'. Valid values: Running, Succeeded, Failed, DatasetFetchRetryScheduled, PartiallySucceeded."
}Responses may also include a traceId. Quote it when you contact support. A malformed parameter, such as a processId that isn't a UUID, returns an errors object naming each invalid parameter.
| Status | When | What to do |
|---|---|---|
400 Bad Request | An invalid parameter, such as an unknown status, a malformed date, an unknown include value or a pageSize outside 1 to 200. | Fix the parameter named in detail or errors. |
401 Unauthorized | The X-Api-Key header is missing, or the key is wrong or has been revoked. | Check the header name and key. Contact the AutomatedOn support team for a new key if it was revoked. |
404 Not Found | The run or record doesn't exist, or has been cleared from history. | Don't retry. See below. |
429 Too Many Requests | More than 60 requests in a minute with the same key. The body is plain text, not JSON. | Wait until the next minute and retry. |
500 Internal Server Error | Something unexpected went wrong. | Retry later. Raise a ticket with the traceId if it keeps happening. |
Something I fetched before now returns 404
Run history is only kept for a limited time, and administrators can delete a month's history. A run or record you fetched earlier can later return 404. If you need a permanent record, store what you need on your side when you fetch it.