Replay Workflow Execution
POST/api/automation/workflow-executions/:execution/replay
Retry a past execution with the same trigger payload. A new execution record is created and queued asynchronously - the original execution is untouched; the new one records it as retry_of_execution_id.
settings:writeGrant this scope to your token under Settings → Developer → Personal Access Tokens.
Body (all optional):
workflow-current(default) runs the workflow as it is saved now;originalruns the definition the retried execution used (its stored snapshot).from_failed_step- boolean, default false. When true and the execution failed, the steps that completed are not run again: their recorded outputs are reused and the run resumes at the step that failed. Ignored for an execution that did not fail (it is retried from the start).
Returns 403 when workflow automation is disabled for the account, 422 for an invalid workflow value.
Path param: execution = execution id to retry.
The workflow's current previewMode governs the retry - not the original run's.
Request
Responses
- 200
- 401
- 403
- 404
- 422
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden
Response Headers
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Validation failed — the body is a field → messages map (Laravel shape) or the platform envelope with a stable machine-readable code. Fix the payload and resubmit.
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.