We automatically retry all webhooks by default using an exponential backoff strategy. This means that each retry attempt is delayed progressively longer than the previous one. The first retry occurs after a short delay, the second after a longer delay, and this pattern continues with exponentially increasing intervals.

Automatic Retry Logic

Requests are automatically retried up to 50 times unless one of the following status codes is received, indicating that further retries are unnecessary:

• 400 (Bad Request)

• 401 (Unauthorized)

• 403 (Forbidden)

• 404 (Not Found)

If any of these status codes are returned, the retry process will stop immediately to prevent redundant attempts.

Managing Request Overload

If your server returns a 429 (Too Many Requests) status code, our system will increase the delay between subsequent retries. This extended delay helps manage server load and prevents further overwhelming your server with repeated requests.

Customizing Retry Intervals

To have more control over when retries occur, we support the Retry-After: <delay-in-seconds> header. This header specifies the number of seconds to wait before attempting the next retry, allowing you to manage the timing of retries according to your server's capacity and processing needs.