One of the many benefits of the Ocrolus API is a retry mechanism for webhook events. If a 'success' 200 HTTP response code is not received, Ocrolus will initiate a retry mechanism, resending the webhook event up to three times over a three-minute period. This webhook event retry service helps provide reliability and event recovery when network problems occur and during client-side service interruptions and deploys.
How many and at what interval does Ocrolus retry webhook notifications?
Our notification system will retry delivery attempts three times approximately three minutes apart, before marking a notification delivery as failed.