We believe we've found a bug in Vapi end of call report webhook end call functionality. There's a strange inconsistency where a call is made, and when the call is either declined or unanswered Vapi may or may not make the "End of Call Report" webhook to the server. Sometimes it does, and frequently it does not. We have looked into the webhook logs and can confirm that in fact the webhook is not even made at all in the circumstances where no "End of Call Report" is received by our server. Can you please take a look at this bug as this may be affecting many of your customers. thanks,

Hi, could you please provide a call id where you experienced this issue? We would like to review the logs to identify the cause.

Hi Praveen here's a list call ids that you can investigate to provide insight into why we in those instances we did not receive an 'end-of-call-report'.

58bebecf-e691-41f4-a247-62aa09695a08,
1d182ffc-724b-4ad8-87f1-d50f3db7414a,
33739288-34d1-45c0-bdc3-d5d26350309d,
6f6d62cb-6cc6-4032-840d-5b5c455fa734,
e5933bb1-6b24-4944-b075-0779a860ca5a,
d91b2a7d-c3f8-4212-bf9b-8ba3167b0e39

Hey Jeremy L, I wanted to let you know that we're managing a high volume of support requests at the moment, so our response time might be a bit slower than usual. I truly appreciate your understanding and will get back to you as soon as possible!  Thanks again for your patience!

No worries, thanks for your heads up

There have been some updates to our platform that may address this. Could you please check if you are receiving end-of-call reports now?

Thanks Kyle, on our initial assessment it seems like the 'end-of-call-report seems to be working again where calls are declined or not answered. However, on our server we have put some tactical fixes so that we could continue to construct a similar object for our post call analysis and reporting. Before we revert our code changes to use the standard 'end-of-call-report' Vapi event again, is there any change logs, patch logs or internal information that confirm there has been an explicit fix for this bug? We don't want to revert changes and then randomly experience this issue again as it will impact our customer experience. We do want to obviously leverage this vapi event over doing it in our own tactical way as it's far simpler and ensures we're always consuming the most up to data post call data schema and relies on vapi official end of call event but we just want some confidence that a fix has been put in to address this issue.

There is a fix for it, however I just checked the repository and looks like the fix specifically has not been merged yet. Keep your current tactical fixes in for now so you are not blocked and we will reach out once the fix has been officially deployed. Cheers

Thanks Kyle. Is there an ETA on when this fix will be merged and redeployed into production?

I don't have an exact ETA for when the fix will be merged and redeployed into production. However, I can assure you that we're working on it and will keep you updated as we make progress.

All good thanks for the headsup. Have the fixes been redeployed?

It has been merged. Please check again and let us know if you are still experiencing issues

Awesome thanks for following up Kyle

Hey Jeremy, It looks like these calls didn't start, so the end-of-call report never sends. This behavior is intentional since end-of-call reports only send after a call has started and connected successfully. To get status-updates of the call through a webhook to see if calls successfully start or are unsuccessful, you can use the

status-update

webhook.