https://retellai.com/?utm_source=discord&utm_medium=seo logo
We are experiencing the chat_ended/chat_analyzed e...
# ❓・ai-evy-support
s
@AI Evy We are experiencing the chat_ended/chat_analyzed events firing too soon from the webhook, or the req.body.chat object is not the most recent. The request object we are getting isn't complete based on the collected_dynamic_variables. This started happening for us in mid January. Also receiving lots of duplicate call_analyzed events
a
Thanks for tagging me @skitRobot. I'll look through relevant sources and get back to you shortly.
### Answer Based on the available documentation, I don't have specific information about timing issues with `chat_ended`/`chat_analyzed` events firing prematurely or incomplete
collected_dynamic_variables
in webhook payloads. What the documentation does confirm about webhooks: - The webhook has a 10 second timeout. [(1) ]() - If no success status (2xx) is received within 10 seconds, the webhook will be retried up to 3 times. - Webhooks are triggered in order but are not blocking — for example, if
call_started
webhook fails,
call_ended
can still trigger. The retry behavior could potentially explain the duplicate
call_analyzed
events
you're seeing — if your endpoint doesn't return a 2xx response quickly enough, Retell will retry. For the issues with incomplete data and events firing too soon, I'd recommend reaching out directly to Retell support, as this sounds like it may be a bug or infrastructure issue that started in mid-January. Check out these potentially useful sources: - [Webhook Overview]() - [Post Call Analysis Overview]() You can also contact the team via [Contact Sales]() or check [GitHub]() for any known issues.
​ To learn more, see the sources I considered: [[1] 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.