Webhook Retry

We provide an exponential retry mechanism where retry attempts are made at progressively increasing intervals if a POST request to your server fails due to a network or destination server issue. A retry would be triggered when a webhook request returns a non-2XX status code, i.e. 4XX or 5XX error codes, in the response. With every retry, a new signature and timestamp are generated and a total of 6 retry attempts would be made in the following delays.

• 0.5 minute
• 1 minute
• 2 minutes
• 4 minutes
• 8 minutes
• 16 minutes

🚧

Maximum Retry Count: The maximum number of retries is set to 6 with the expotential retry interval = 0.5, 1, 2, 4, 8, 16 minutes.

FIFO Order: For FIFO Events, the retry attempts will be processed in the same order they were triggered, ensuring First-In-First-Out (FIFO) delivery.

Message Loss: If the message fails to deliver after 6 retries, it will be dropped and no further attempts will be made to resend it.

Handling High Volume of Requests: In the event of frequent webhook delivery failures, be aware that a backlog of message may build up. This could result in a sudden surge of requests to your server when it recovers. It's advisable to ensure that your system can handle this scenario to prevent any service disruption or overload.

Continuous Delivery Failure

If webhook delivery continues to fail with the error codes like 404, your endpoint will be unsubscribed from webhooks. An alert email will be send to both the organization's email address and any custom email addresses configured with the webhook. After resolving the issues, you will need to re-enable the webhook endpoint through the admin panel.