Hi VAPI team, I'm experiencing an intermittent issue where end-call webhooks are not being generated at all for some of my calls. When I query the /call/{id} endpoint, these calls show "endedReason": "customer-did-not-answer", indicating they have properly ended. However, when I check the /logs endpoint filtered by specific call IDs, no webhook events were generated (as shown in the attached screenshot). the webhooks are not being created/triggered by VAPI Below are some example call IDs where this issue occurred: 391b275c-5403-4787-b889-b002d5209193 624c8c50-504f-4f1c-8d11-a26f4623ea55 28b27174-9da0-4940-978f-1bcd8689ec82 66f5508c-9909-46f9-81b5-67fe453e00ed Could you please investigate why these webhook events are not being generated consistently? Thanks for your assistance. https://cdn.discordapp.com/attachments/1379619795171016775/1379619795510628433/image.png?ex=6840e68f&is=683f950f&hm=ec26b48f5400669aa31024e8198c5bbd6fda874fbfef4632219a86590f63cb02& https://cdn.discordapp.com/attachments/1379619795171016775/1379619795858751578/image.png?ex=6840e68f&is=683f950f&hm=1046830baeeef02b0de3652c2a41ae83b52461bbf410950f52a35e9543cc3396&

This is a known intermittent issue with Vapi where end-call webhooks are sometimes not generated, even though the call ends with a valid

endedReason

like "customer-did-not-answer". There is no documented fix, but the Vapi team recommends providing affected call IDs and details to support for investigation. Please reach out to [Vapi Support](https://docs.vapi.ai/support) with your call IDs and account information so they can look into backend logs and help resolve the inconsistency. If you have recently changed any SIP trunk or webhook configurations, mention this as it may help narrow down the cause. Sources: - [Vapi outbound call not triggering (Discord)](https://discord.com/channels/1211482211119796234/1341449578100031488) - [Vapi webhooks not sent (Discord)](https://discord.com/channels/1211482211119796234/1326809606671958080) - [Vapi call log empty data (Discord)](https://discord.com/channels/1211482211119796234/1334154920214921238) - [Vapi Server Events Documentation](https://docs.vapi.ai/server-url/events) - [Vapi Call Ended Reasons](https://docs.vapi.ai/calls/call-ended-reason) - [Vapi Support](https://docs.vapi.ai/support)

Vapi may not trigger end-of-call-report webhooks for calls with endedReason: "customer-did-not-answer"; instead, rely on status-update events to detect call endings and verify your server URL is correctly set..

In my case, the status-update event is correctly configured on my assistant — I’m receiving multiple updates as expected. However, there are a few calls where I don’t receive any status-update at all. That’s why I believe this might not be a configuration issue. Please see the attached screenshots for reference. https://cdn.discordapp.com/attachments/1379619795171016775/1379830961763651745/image.png?ex=6841ab39&is=684059b9&hm=7b1b041f5560799fbb01635f33c5bb00e830b2b7f3e312d698a69f2c2f5a60cd& https://cdn.discordapp.com/attachments/1379619795171016775/1379830962225152191/image.png?ex=6841ab39&is=684059b9&hm=1dcaec68ec2405f9e17130bb6e413e5b1003920994e691f3bd81b30b331c2748& https://cdn.discordapp.com/attachments/1379619795171016775/1379830962791252068/image.png?ex=6841ab39&is=684059b9&hm=c5a47281e6a6582dc142f22cc21721f8f5708dd92034e34db728f803910548cb&

We don't trigger end-of-call-report incase call wasn't answered. Can you use status-update for it?

As I mentioned above, the status update event isn’t being received for some calls when they are not answered, even though it’s correctly configured in my assistant. Other calls do receive the event, so it seems to be an intermittent issue.

Hey Andre, we don't send status update events for these calls never connected from telephony side/ https://cdn.discordapp.com/attachments/1379619795171016775/1381645238803759225/image.png?ex=684844e6&is=6846f366&hm=5d78921ee77c83229c8dad18d91ac527d930580331754dcd70e4f0b56537b9ea&

Got it. But since I need to manage the concurrency slots on my side, I always need to update the call status. If I don’t receive it via webhook, I’ll need to keep polling your API to check it. I don’t think it’s the best solution, but given that, I’ll follow this approach.

Hi André, Thanks for pointing this out. I know this is not the best approach, but we have already raised this to the team, so it will be fixed soon. Where you will have a status update event for all types of calls. Thanks for patience. You will get to know through announcements once this is fixed.

Thanks! I’ll keep an eye on the announcements.