Webhook Retry Policy | Classic

Contentstack follows an exponential webhook retry policy whenever any webhook fails to send data to the desired notification URL or a session timeout occurs.

Note: Contentstack waits for 30 seconds to receive data from the destination server. If the destination server fails to send data within this timeframe, then the webhook request is timed out.

The exponential retry policy attempts to send data to the destination URL again four more times after certain intervals. Setting a resend interval avoids several requests constantly hitting the server and prevents database overload.

Contentstack sets the resend interval time to 5 seconds, by default, for the first retry attempt. The interval time then increases exponentially according to the retry instance. The exponential backoff formula will look as follows:

{resend_interval} + {retry_instance} ^ 4

For instance, if the resend interval lasts for 5 seconds and the webhook can retry sending data four more times, then the exponential backoff strategy will calculate retry intervals as follows:

Retry Instance No.

Next Resend Interval (seconds)

1

5

2

25

3

125

4

625

If the webhook request fails to run successfully after the last retry attempt, Contentstack stops retrying and marks the request with a failed status. You can view the webhook logs to get more details on the failed request.

Was this article helpful?

Thanks for your feedbackSmile-icon

On This Page

^