Retry API rate limit errors with exponential backoff and a maximum attempt count, while keeping the original checkout failure separate from the alert delivery record. For a media subscription checkout, incident reconstruction is the deciding constraint: a throttled notification must not erase the evidence of a failed purchase.
TL;DR: detect HTTP 429, reuse one delivery identifier across retries, honor Retry-After when supplied, and stop after a defined budget. Preserve the final delivery outcome beside the original event so an operator can distinguish a checkout failure from a notification that never arrived.
How should an alert integration handle API rate limit errors without losing evidence?
Start with two records. The checkout record describes the failed workflow; the delivery record describes the effort to tell someone about it. A single generic error message mixes those jobs together.…