# Webhook Timeouts

Truecaller for Business implements three distinct timeouts for webhooks to ensure reliable and efficient delivery of notifications:

* Connection Timeout: This timeout governs the duration allowed for establishing the initial connection to your webhook URL's HTTP server.
* Read Timeout: Once the connection is successfully established, this timeout sets the maximum waiting period for reading data from the HTTP server at any point during the process.

The values for each timeout are as follows:

| Timeout            | Duration |
| ------------------ | -------- |
| Connection Timeout | 20,00 ms |
| Read Timeout       | 20,00 ms |

Webhook execution can fail due to timeouts or errors.\
For each event where webhook call fails, the calls are retried up to 7 times based on the following schedules:

| Retry | Time                                |
| ----- | ----------------------------------- |
| 1     | 2 minutes after the failure         |
| 2     | 6 minutes after the previous retry  |
| 3     | 30 minutes after the previous retry |
| 4     | 1 hour after the previous retry     |
| 5     | 5 hours after the previous retry    |
| 6     | 1 day after the previous retry      |
| 7     | 2 days after the previous retry     |

<mark style="color:$primary;">These details are mentioned in the webhook event page.</mark><br>

<figure><img src="/files/rWhirT52dG0ut1bSv0RG" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.truecaller.com/truecaller-for-business/verified-business-api-documentation/webhooks/webhook-timeouts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.