AutoVerse Workflow Controller icon

AutoVerse Workflow Controller

Enterprise workflow orchestration, execution control, and monitoring for n8n

Actions44

Execution → Retry Execution

AI-generated

Summary

Retries a single n8n execution by ID via the n8n public API (POST /executions/{id}/retry), choosing whether to rerun with the currently saved workflow or the original workflow snapshot.

Inputs

  • Execution Name or ID (executionId) (required) — The execution to retry. Pick from a list of the most recent executions (labelled with ID, status, workflow name, start time) or enter an ID/expression. Errors if empty.
  • Retry Mode (retryMode) — 'With Currently Saved Workflow' (default, sends loadWorkflow=false) or 'With Original Workflow' (sends loadWorkflow=true).

Output shape

One item per input item with JSON: { executionId, retryMode, response }, where response is the raw body returned by the n8n retry endpoint.

Uses the required n8nApi credential. Transient API errors (408, 425, 429, 5xx) are retried up to 3 attempts with backoff before failing. On failure the node throws, or emits { error } if Continue On Fail is enabled. The retry is triggered but the node does not wait for the new execution to finish; combine with Live Execution Polling to track it.

Examples

Example 1: Retry a failed execution after fixing the workflow

Execution = the failed run ID; Retry Mode = With Currently Saved Workflow.

Example 2: Re-run a failed execution exactly as originally defined

Execution ID from an expression such as {{$json.executionId}}; Retry Mode = With Original Workflow.

Links

Discussion