Sachin Jaiswal
10/20/2025, 5:07 AMChiranjeet Mishra
10/20/2025, 5:07 AMVapi Support Bot
10/20/2025, 5:08 AMVapi Support Bot
10/20/2025, 6:33 AMGIDEON
10/20/2025, 6:34 AMSachin Jaiswal
10/20/2025, 8:55 AMSachin Jaiswal
10/21/2025, 1:09 AMGIDEON
10/21/2025, 1:57 AMGIDEON
10/21/2025, 2:02 AMSachin Jaiswal
10/21/2025, 2:12 AMChiranjeet Mishra
10/21/2025, 6:43 PMendedReason in your [call logs](https://dashboard.vapi.ai/calls). This can help identify if the issue is related to assistant logic, connectivity, or configuration errors. For example, if it ends with silence-timed-out, the call was terminated due to prolonged silence.
To investigate, consider the following steps:
1. **Review Call and API Logs**: Navigate to Observe > Call Logs and Observe > API Logs in your dashboard to check call details and any related API errors.
2. **Check Debugging Resources**: Utilize the [dashboard testing features](https://docs.vapi.ai/debugging) like running automated tests, testing individual tools, and monitoring webhook logs.
3. **Verify Assistant Configuration**: Ensure that all necessary configurations and settings, like assistant ID and tool integrations, are correctly set up.
For detailed analysis, you can refer to this [guide on call ended reasons](https://docs.vapi.ai/calls/call-ended-reason) and [troubleshooting common issues](https://docs.vapi.ai/debugging).
If you need further assistance, providing the Call ID and a description of the expected vs. actual behavior can help in diagnosing the issue more effectively.Sachin Jaiswal
10/22/2025, 12:46 AMSachin Jaiswal
10/23/2025, 3:22 AMChiranjeet Mishra
10/24/2025, 12:26 AM"endedReason": "call.in-progress.error-assistant-did-not-receive-customer-audio"
This is indicating that the assistant did not hear the user, so it ends the call.
For the other call ID, it’s a rare case where the worker process unexpectedly stopped. This shouldn’t happen again, but if it does, please let us know right away so we can investigate further.Sachin Jaiswal
10/24/2025, 2:31 AMSachin Jaiswal
10/24/2025, 2:33 AMChiranjeet Mishra
10/27/2025, 10:24 PM