An n8n retry can repeat an email that the provider already accepted. Prevent duplicate sends at the business-effect boundary rather than treating a new execution identifier as a new customer message.
Execution retry and message identity differ
A workflow execution is one run of orchestration. An email intent is the business decision to send a particular message for a particular event. Several execution attempts may belong to the same email intent.
For a proposed demonstration, create a durable message-intent record before the send. Give it a stable identity based on trusted operation references and message purpose. Track prepared, submitted, confirmed, failed, and uncertain states as appropriate to the email provider’s contract.
n8n’s error-handling documentation describes error workflows and execution investigation. Those features support recovery, but they do not establish that a repeated external send is automatically duplicate-safe.
Test a fictional post-send timeout
A request-confirmation email reaches the provider, but the response is lost before the workflow records completion. A retry sees an uncertain send. It should use supported provider evidence or duplicate protection before sending again, not assume the first attempt failed.
A local unique message-intent record alone cannot prevent every duplicate if the external provider has no matching idempotency or reconciliation mechanism. Document that uncertainty and route consequential cases for review rather than promise exactly-once email delivery.
| Failure fixture | Required observation |
|---|---|
| Failure before send | Eligible retry retains the same intent |
| Provider accepts, response lost | Reconciliation before another effect |
| Two workers process same intent | One current execution permission |
| Operator retries execution | Existing message state remains authoritative |
| Customer requests a new resend | Explicit new intent under the approved policy |
Use a fake mail sink and controlled timeouts. Assert accepted-message count as well as n8n execution status. Two green runs can still represent an unwanted duplicate email.
Keep recovery visible to operators
The staff view should show whether the message is pending, failed, or uncertain and what action is permitted. A generic “retry all” process can repeat already completed effects in other steps of the same workflow.
A durable outbox adds storage and state-management work. For low-impact notifications, the business may accept a bounded duplicate risk, but that decision should be explicit and measured. Do not imply an untested workflow has stronger guarantees than its provider contracts.
This demonstration design is proposed, not a claim of a deployed n8n client workflow. The voice integration case study describes relevant backend work. See partial-success handling.
n8n email retry FAQ
Is the execution ID a suitable email key?
Not alone. Retries or manual reruns may create different execution identities for the same business message.
Does an error mean no email was sent?
No. The provider may have accepted it before the response failed.
What proves duplicate protection?
A controlled failure test and destination-side effect count under the actual supported sending contract.