Software retries work because networks are unreliable. A request times out, a worker restarts, or a response disappears before the application records it. Trying again is often the correct engineering decision.
Email creates a special problem: the first request may have succeeded even when the application never received the confirmation. A blind retry can send the same receipt, password link, alert, or welcome message twice.
The customer sees duplication. The system sees two successful requests.
Transactional email needs a retry design that separates “try the request again” from “send another message.”
Understand the ambiguous failure
Imagine an application sends a receipt through an email API. The provider accepts the message and returns success, but the network connection drops before the application receives the response.
The application cannot tell whether the provider accepted the request.…