Server message "customer-didn't-answer" has been removed suddenly. Unable to track these calls and take action.

HeyEeshita Thank you for creating the ticket! A member of our team will reach out to you shortly.

@Eeshita I'm sorry to hear that you're experiencing issues with tracking calls when the customer doesn't answer. It sounds like there might be a problem with the event notifications or a change in the system configuration. To assist you further, could you please provide more details about how you were previously tracking these calls and any changes that might have occurred in your system setup? This information will help me understand the situation better and offer a more accurate solution.

@Vapi these were being tracked using the server message "customer-didn't-answer" provided by vapi to the server url .

@Eeshita Thank you for providing that information. It seems like there might be an issue with the event notification for the "customer-didn't-answer" message. To resolve this, we should check the configuration on the VAPI Dashboard to ensure that the server URL is correctly set up to receive this specific event. Could you please verify if the server URL in the Account page on the VAPI Dashboard is correctly pointing to your endpoint that handles the "customer-didn't-answer" messages? If the URL is correct, we may need to look into the server logs to identify if the messages are being sent from VAPI but not received by your server, or if there's an issue on the VAPI side. If you have already checked and the configuration seems correct, please let me know so we can investigate further.

@Vapi Yes , other server messages are responding correctly.

@Eeshita Understood. If other server messages are working correctly, but the "customer-didn't-answer" message is not being received, it's possible that there may be an issue specific to that event type. To address this, I recommend the following steps: 1. Double-check the event subscription settings for the "customer-didn't-answer" message to ensure it is still active. 2. Review any recent changes to the system that might have affected the handling of this specific message. 3. Check the server logs to confirm that the message isn't being received at all, rather than being received but not processed correctly. 4. If you have access to the VAPI Dashboard, look for any alerts or notifications that might indicate a problem with the event delivery system. If after these steps the issue persists, it would be best to reach out to VAPI support directly for a more in-depth investigation. They may need to check the backend systems to understand why this particular message isn't being sent or received as expected. Would you like me to assist you with anything else at this moment?

@User could you help here

Hey @Eeshita To help track down this issue, could you share: - The call ID This would really help me figure out what went wrong!

@Shubham Bajaj 3b4d8b85-7abd-4fca-a6b7-b1ac5034dc71 , 6a426c09-a19e-4572-9220-673b675cab0e

🔵 06:42:18:916 Call

3b4d8b85-7abd-4fca-a6b7-b1ac5034dc71

Waited 300s But Transport Never Connected. 🔵 06:37:50:163 Call

6a426c09-a19e-4572-9220-673b675cab0e

Waited 300s But Transport Never Connected. @Eeshita These calls failed because of Twilio failed to respond in required time, and then eventually you never recieved any status update events. We will be working on this status-update events to be triggered even when calls are never connected.

Thanks for the update .

@Eeshita can you try making calls now, and let me know how it goes

Will test and let u knw