API Reference
Retry automation run
Retry a failed run from its failed step
On this page
This endpoint retries a failed execution from its failed step: steps that already succeeded are not re-executed, so any side effect they already caused (an email already sent, a row already written) is not repeated. Use it after fixing what made the run fail — a reconnected account, a recovered external API — instead of waiting for the next trigger event. The failed step and everything after it then run for real, completing the original event's work.
Take the run's id from List automation runs. A retry resumes the same run — it does not create a new one.
Path Parameters
idstringrequired
The ID of the automation (from List automations)
run_idstringrequired
The ID of the failed run (from List automation runs)
This endpoint takes no request body.
Response
run_idstring
The retried run's ID (the same run that was passed in)
statusstring
The run's status right after the retry (e.g. RUNNING, or SUCCEEDED when it finished instantly)
notestring
Confirmation that already-succeeded steps were not re-executed
A missing automation or run — or one that does not belong to your account — returns a 404.
Error codes (422)
error |
Meaning |
|---|---|
retry_no_op |
The retry did not resume the run — its saved state is stale, most commonly because the run passed through a Delay step before failing. Such a run cannot be resumed as-is; the message lists the safe options (repair the automation, or wait for its next real trigger event). |
retry_failed |
The retry could not be started — try again shortly. |
{
"run_id": "yHhXbqWj3zJZ5ztDNfUry",
"status": "RUNNING",
"note": "Retried FROM the failed step — steps that already succeeded were NOT re-executed, so their side effects were not repeated."
}
{
"message": "The retry did not resume this run (its status is still 'FAILED') — its saved state is likely stale, most commonly because the run passed through a Delay step before failing. This run cannot be resumed as-is. To force a fresh full run (re-executes EVERY step, including any that already sent a message/email/call — get the user's explicit confirmation first, then rebuild via update-automation's repair path), or otherwise wait for the automation's next real trigger event.",
"error": "retry_no_op"
}
{
"message": "Run not found for this automation.",
"error": "not_found"
}
Related guides
API Reference
Introduction
Welcome to the VoxLink API
Read guide →API Reference
Authentication
Learn how to authenticate your API requests
Read guide →API Reference
Get current user
Get the authenticated user's profile information
Read guide →API Reference
List assistants
List all assistants for the authenticated user with pagination
Read guide →