Email Send Retries
Learn when Simply Send retries a failed email, what the API response means, and how to check the final result in Email Events.
What this setting does
Email send retries let Simply Send take responsibility for eligible temporary server errors that occur while it is processing a send request. The feature applies to supported API and SMTP submissions. It does not cover marketing messages already being processed by a marketing queue.
The setting is managed in the workspace configuration. An administrator can set the global default for workspaces. A user with permission can override it for a specific workspace.
Which errors are retried?
Retries apply to eligible 5xx errors during the send phase. When automatic retry is enabled, Simply Send may retry an eligible submission whose provider acceptance could not be confirmed. An ambiguous retry can result in a duplicate. When Simply Send returns DELIVERY_AMBIGUOUS, check Email Events before resending. Request errors such as invalid addresses and other 4xx responses are excluded.
This is not a retry for every possible 5xx. It applies only when Simply Send can safely capture and manage the send attempt. If Simply Send cannot capture the request, the original error is returned.
Choose a retry mode
| Mode | What happens |
|---|---|
| Disabled | Simply Send returns the send error. You can decide whether to submit the request again. |
| Automatic retry | Simply Send retries eligible failures within the configured attempt limit and deadline. |
| Manual review and retry | Simply Send saves the failed email for review. A user with permission can review it and start a retry. |
What the API response means
When Simply Send successfully captures an eligible failure, the API returns 202 Accepted with the email ID and a pending status. This means Simply Send has accepted responsibility for the configured retry or review process; it does not mean the email has already been delivered. Do not submit that accepted request again. Use the returned email ID to find the same email in Email Events.
HTTP/1.1 202 Accepted
{
"success": true,
"data": {
"emailId": "email_...",
"status": "pending"
}
}If retries are disabled, the send fails, or Simply Send cannot capture the request, the API returns an error response. Review the error before deciding to submit again.
Attempts and saved email content
Automatic retry settings control the maximum total attempts, including the original send, and the time limit for retrying. The available ranges are 2–10 total attempts and 1–60 minutes. The default settings are 10 total attempts within 10 minutes. Retries stop when the email is accepted by the provider, the attempt limit is reached, or the deadline passes.
Manual review keeps the captured email content available while it awaits review. By default, content is deleted when retry processing ends. Enable five-day retention if you need to keep it for audit, including after a successful send.
Check the outcome
- Open the workspace’s Email Events page and search for the email ID from the response.
- While automatic retries are running, the email appears as Retrying, with retry details in the email details panel.
- In manual mode, open the email details and review the captured email before selecting Retry.
- If a retry succeeds, the same email record is updated and its delivery events appear there.
- If attempts are exhausted or the deadline passes, the same email record is marked Failed and a final failure event is published. You can then decide whether to retry it yourself.
Email events can take a short time to appear after processing. Refresh the email details or Email Events page if the latest status is not visible yet.
Before you submit again
If the API returned 202 Accepted, do not resubmit the same email while Simply Send is retrying or holding it for review. Wait for the final status in Email Events. If the request returned an error instead, check the email record first when available; only retry once you know Simply Send did not accept it for managed retry.

