Moody Reaper
07/19/2024, 8:55 AMe5967593-3182-4451-8938-859ec746fd3b
- 88a82516-44d5-4a0f-8fee-22b420360d49
- 427ba882-96eb-41e2-9133-a156ae2ae920
- e1212b0b-17f9-455e-8406-ae80e493a820
- f4d609f9-85ed-41b3-803c-7be1ac8880db
We can see the following "Ended Reason": unknown-error
Also, some call logs contain the following:
status-update Server URL Error: timeout of 20000ms exceeded
Our backend does not get any events, we get only the following response:
json
{
"message": {
"type": "status-update",
"status": "ended",
"endedReason": "unknown-error",
// ...
"timestamp": "2024-07-18T23:20:32.800Z"
}
}Vapi
07/19/2024, 8:56 AMunknown-error ended reason and the timeout error in the call logs suggest there might have been a temporary service disruption or a network-related issue that prevented the calls from being successfully processed.
To assist you further, I would need to check the system logs for the specific time interval you mentioned and the call IDs provided. However, as a support bot, I don't have direct access to the system logs or the ability to investigate past events.
For now, I recommend checking the following on your end:
1. Review your server logs around the time of the incidents to see if there were any internal issues that could have caused the timeouts.
2. Ensure that your server's firewall or any security settings are not blocking or throttling the connections.
3. Verify that your backend services were operational during that time and that there were no deployments or changes that could have affected the service.
4. Check with your internet service provider to see if there were any known network issues at the time.
If the problem persists or you need further assistance, please reach out to the VAPI support team with the call IDs and the specific time frame of the incidents. They will be able to provide more detailed insights and help resolve the issue.
Would you like me to guide you on how to contact the VAPI support team for further assistance?Vapi
07/19/2024, 8:56 AMVapi
07/19/2024, 8:56 AMShubham Bajaj
07/19/2024, 3:04 PMShubham Bajaj
07/19/2024, 3:04 PMShubham Bajaj
07/20/2024, 3:15 PMupdate:
- e5967593-3182-4451-8938-859ec746fd3b
Failed because of 11labs ws-connection timeout, right before sending the user input to custom llm the customer ended the call.
- 88a82516-44d5-4a0f-8fee-22b420360d49
same as previous
- 427ba882-96eb-41e2-9133-a156ae2ae920
can you please CA90ff828a047afff67d580a5eda304d81 check the log over twilio console to confirm error reason, as per our system the call was never started by twilio and eventually call status changed from queued to ended.
- e1212b0b-17f9-455e-8406-ae80e493a820
same as previous CA50c53c518c1898b7ed06637c6abe2cfe
- f4d609f9-85ed-41b3-803c-7be1ac8880db
For this the custom-llm didn't responded after 23:27:04:855 for CustomLLMRequest which eventualy resulted into timeout and later as 'pipeline-error-custom-llm-failed'Shubham Bajaj
07/23/2024, 8:25 PM