Event Delivery & Retry Logic

View as MarkdownOpen in Claude

We are committed to reliable event delivery, even in the face of temporary network issues or service disruptions. Our system automatically retries failed webhook deliveries using a progressive backoff strategy to maximize success without overwhelming your infrastructure.

Retry Behavior

If a webhook delivery fails due to a connection issue or a non-2xx HTTP response, we will retry the request up to 11 additional times over a 24-hour period, using exponential backoff with jitter.

Retries use exponential backoff with full jitter, meaning each retry will occur randomly between 0 and the maximum delay for that attempt — helping spread load and prevent retry bursts.

AttemptApproximate Delay (± jitter)
InitialImmediate
Retry 11 minute
Retry 22 minutes
Retry 3+Doubles with each attempt
Final~24 hours after initial try
We use exponential backoff with full jitter to help ensure high delivery success without retry storms or system overloads.