Mechanism for resending webhooks

Step 1: Record the unsent web hook in the database

When your web hook cannot reach its target for some reason, it gets recorded in a table with a mark of unsuccessful delivery.

Step 2: Keeping track of retry attempts

Separately, the number of retry attempts for each unsent web hook is recorded.

Step 3: Attempt to resend the web hook

When the web hook ends up in the queue for resend, it is taken for processing. The resend happens according to the following algorithm:

1. The delay time before each retry is calculated using the formula: 2^n, where 2 is the number of seconds, n is the number of retry attempts.
2. The value of n reaches a maximum limit of 15 attempts, after which if there are 15 unsuccessful deliveries, the web hook will no longer try to resend.
3. Approximately 9 hours pass between the 14th and 15th delivery attempts.
4. In total, it takes about 18 hours for 15 retry attempts.

Also see:

Webhooks

POST request

GET request