Short answer: make recovery the design constraint: keep one delivery ID across every attempt, classify failures before retrying, use capped exponential backoff with jitter, and send exhausted work to a dead-letter queue that operators can inspect and redrive safely.
Consider a property-management SaaS sending a lease.payment_recorded webhook to an accounting integration. The useful data flow is event store to queue to delivery worker to recipient, with a delivery ledger recording each transition. A timeout leaves the sender with an uncomfortable fact: the recipient may have applied the payment even though the worker never saw the response. A queue retry policy controls when another request runs. It cannot, by itself, prevent that request from repeating the business effect.
That distinction drives the whole design.
What should a simple queue retry policy preserve for SaaS background jobs?
Start with the recovery record, not the delay formula.…