> For the complete documentation index, see [llms.txt](https://docs.mdintegrations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mdintegrations.com/changelog/2026/webhook-delivery-reliability-and-retry-overhaul.md). # Webhook Delivery Reliability & Retry Overhaul *Released February 24, 2026* Webhook delivery infrastructure improvements covering reliability, retry consistency, delay handling, and failure tracking/observability. This is an internal change — no partner action is required and no downtime is expected. These changes were available in the UAT environment ahead of the production release. ## \[Timeout Policy] * Webhook timeout is 15 seconds. If your endpoint doesn't return HTTP 200 within 15 seconds, the delivery is considered failed and a retry is initiated. ## \[Retry Strategy] * 1st retry: 15 minutes * 2nd retry: 30 minutes * 3rd retry: 1 hour * 4th retry: 4 hours * 5th retry: 8 hours * 6th retry: 11 hours * Retries span a 24-hour period total. If all retries fail, the webhook is marked permanently failed. ## \[Webhook Request Format] * Payload/header structure is unchanged; internal delivery handling was improved for more predictable behavior. ## \[Recommended Best Practices] * Respond with HTTP 200 as soon as the webhook is received and validated * Avoid long synchronous processing inside your webhook endpoint * Process payloads asynchronously when possible --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.mdintegrations.com/changelog/2026/webhook-delivery-reliability-and-retry-overhaul.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.