Retry a failed message
POST/v1/outbox/:queueId/retry
Puts a message whose delivery failed for good back into the queue with a fresh set of delivery attempts. Only a failed message whose content is still stored can be retried: the content of the most recent failures is kept for this, within the bounds set by the queueKeepFailedContent and queueKeepFailedContentSize settings (or EENGINE_QUEUE_KEEP_FAILED_CONTENT and EENGINE_QUEUE_KEEP_FAILED_CONTENT_SIZE, which win when set). A message that cannot be retried answers 409 with code NotFailed (the message is not in the failed state) or ContentGone (its content is no longer stored).
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 429
- 500
Returns a retry marker. The message is waiting for a delivery attempt again.
Invalid input - the path parameters, query arguments, or request payload did not pass validation. Also returned when the email server refused the request, in which case the response carries a code and the server response instead of a field list
Authentication failed - the access token is missing, invalid, or was not accepted
Access denied - the access token does not grant permission for this operation (token scope, account, or IP address restriction)
Not found - the requested entity (account, message, mailbox, etc.) does not exist
Conflict - the entity is not in a state the operation applies to
Rate limit exceeded - too many requests were made with this access token
Internal server error - an unexpected error occurred while processing the request