Webhook Retry

Definitions

The retry policy used when a webhook delivery fails (non-2xx response or timeout). Good implementations use exponential backoff (e.g., 1min, 5min, 30min, 2hr, 24hr), a maximum retry count, and a dead letter mechanism for permanently failed deliveries. Webhook consumers must be idempotent since retries can cause duplicate deliveries.
In plain English: Automatically resending webhook notifications when the receiving server doesn't respond, with increasing delays between attempts.
Example: "Stripe retries failed webhooks up to 3 days with exponential backoff — make sure your handler is idempotent to handle duplicate events."