### Answer The

call_analyzed

webhook can trigger multiple times by design [(1) ]() . This is expected behavior - only

call_started

and

call_ended

events are guaranteed to trigger exactly once . The webhook has a 10-second timeout and will retry up to 3 times if it doesn't receive a success status (2xx) within that window [(2) ]() . To prevent duplicate processing on your end, you should implement idempotency handling in your webhook endpoint using the

call_id

to track which calls you've already processed. Here's the recommended approach: 1. Return a 2xx status code immediately (within 10 seconds) to prevent retries 2. Use the

call_id

from the webhook payload to check if you've already processed this analysis 3. Store processed

call_id

values in your database or cache to deduplicate The webhook will POST with this structure :

json
{
 "event": "call_analyzed",
 "call": {
 "call_id": "Jabr9TXYYJHfvl6Syypi88rdAHYHmcq6",
 // ... other call details
 }
}

Implement idempotency checks on your endpoint to ensure you only process each unique

call_id

once, even if Retell sends the webhook multiple times.

​ To learn more, see the sources I considered: [[1] call_analyzed webhook triggered multiple times](https://discord.com/channels/1186424376300679209/1408550487216750634) [[2] Webhook Overview](https://docs.retellai.com/features/webhook-overview) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

### Answer Based on the sources, receiving multiple distinct

call_analyzed

events (not just retries) for the same call is not expected behavior [(1) ]() . The webhook should trigger once per event type per call, with up to 3 retries only if no success status is received . However, there's a documented case where a user experienced receiving 3x the same

call_analyzed

event [(2) ]() . The solution in that case was related to their webhook handling setup in Make.com - removing a trailing Webhook Response (200) module resolved the issue . When they tested with webhook.site, they only received 1

call_analyzed

event, confirming the problem was in their integration configuration, not Retell . To troubleshoot: 1. Test your webhook endpoint with a service like webhook.site to confirm whether you're receiving multiple distinct

call_analyzed

events from Retell or if it's an issue with your endpoint configuration 2. Ensure your endpoint returns a 2xx status code within 10 seconds to prevent legitimate retries [(1) ]() 3. Check your webhook integration platform (if using one) for any response handling or retry logic that might be causing duplication [(2) ]() If webhook.site shows you're genuinely receiving multiple distinct

call_analyzed

events from Retell for the same call, that would indicate an issue that should be reported to Retell support, as it's not documented as expected behavior [(1) ]() .

​ To learn more, see the sources I considered: [[1] Webhook Overview](https://docs.retellai.com/features/webhook-overview) [[2] 3x call_analyzed event at every call.](https://discord.com/channels/1186424376300679209/1325590925597999216) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.