> For the complete documentation index, see [llms.txt](https://docs.truecaller.com/truecaller-for-business/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.truecaller.com/truecaller-for-business/features/call-me-back/why-am-i-receiving-duplicate-webhook-events.md).

# Why am I receiving duplicate webhook events?

The outgoing webhook feature is built with at-least once delivery semantics, which guarantees no data is lost but may result in the same event being delivered more than once.This is expected behaviour.\
In distributed systems, machines can go down or restart before an acknowledgement of delivery is received, so the system resends events to ensure they reach their destination. \
To further guarantee delivery, automatic retries are triggered using an exponential backoff strategy — up to 7 attempts over a 48-hour period.\
To handle this, every event includes a unique `event_id`. Before writing to your database, check whether the `event_id` has already been processed and discard any duplicates. \
This pattern — known as idempotent processing — is the recommended approach for integrating with any at-least once delivery system.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.truecaller.com/truecaller-for-business/features/call-me-back/why-am-i-receiving-duplicate-webhook-events.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.