← Can I Safely Hit Retry? · free tools
Little Life Moths · free reference
Safe Retry Reference
for n8n
A deliberately tiny workflow for the awkward moment after automation failure: do I know enough to retry without doing the side effect twice?
What the example proves
- Three synthetic events enter the workflow.
- One approved event becomes a draft-only simulated write.
- One event stops at a human approval boundary.
- A duplicate
event_idis held rather than processed twice. - A final receipt verifies that every input was accounted for and no outward action occurred.
Executed locally in n8n 2.17.7. The runtime receipt passed every check.
The important limit
The example uses an in-memory Set() to make the duplicate visible and easy to inspect. That only protects one execution. It is not durable idempotency.
Production retry safety may require a persistent idempotency ledger, a provider-supported idempotency key, a unique database constraint, or read/reconcile logic around the external system. If a request times out after a write, the outcome can be unknown. “I got an error” is not the same fact as “nothing happened.”
Four-node shape
- Manual Trigger
- Synthetic Side-Effect Events creates one approved, one unapproved, and one duplicate event.
- Approval + Idempotency Gate refuses duplicates and unapproved work.
- Verification Receipt checks counts and confirms zero outward actions.
This reference has no credentials, customer data, cloud models, HTTP requests, database writes, or production integrations.
Use it as a test fixture, not a talisman
Import the JSON, inspect every node, run it, then replace the synthetic draft with your own rehearsal logic before connecting a real side effect. Add durable dedupe and reconciliation appropriate to the system you are actually touching.
If your question is still “can I retry this particular failed run?”, the browser-only retry triage tool is the smaller first step.
If one real incident needs evidence review
The free tools may be enough. If they are not, the Agent Incident Receipt is a fixed $39 static review of one redacted evidence packet. It does not log into production or run customer code.
Synthetic reference only. Runtime verification shows what this workflow did in the stated test, not a certification of n8n, an external API, or your production system.