Template ownership determines whether a retry still represents the original support request: resolve the marketplace contact form's queue and render its email before dispatch, then keep both fixed through the retry budget. TL;DR: use exponential backoff starting at 2 seconds, cap it at 32 seconds, allow 5 total attempts, honor server retry guidance, and preserve the logical message identity. Retries can improve the chance of API acceptance without overwhelming the service; they do not establish inbox delivery.
The incident lesson to test before production
Consider a bounded production design exercise, rather than a report of an observed incident. Submit one marketplace contact form with category seller_payout , route it to the seller support queue, and inject a rate-limit response before the email is accepted. While that request waits, imagine an editor publishing a revised template and an operator changing the category's queue assignment.…