Our cartesian voice assistant suddenly stopped responding and won't respond after the first message Here are call id: 0199bf9e-0925-733b-946f-fcff7a412451 Here is another one: 0199bf94-742a-700b-ba5b-5977e4e062a2

Thank you for sharing the call IDs (0199bf9e-0925-733b-946f-fcff7a412451 and 0199bf94-742a-700b-ba5b-5977e4e062a2). To help diagnose why your assistant stopped responding after the first message, could you let me know if you observed any error messages or unusual "ended reason" codes in the [Vapi dashboard call logs](https://dashboard.vapi.ai/calls) for these calls? Sources: - [Debugging voice agents](https://docs.vapi.ai/debugging) - [Call ended reasons](https://docs.vapi.ai/calls/call-ended-reason)

Yes one call completely just droped with this reason (call.in-progress.error-vapifault-cartesia-voice-failed)

Cartesia has reported TTS instability, we had the same issue: https://status.cartesia.ai/

@Bathroom King Thank you for your reply, this is very insightful

Hi nightcrawler, If you're experiencing issues with assistant responses or call failures, the problem might be related to configuration errors or possibly an internal issue. Here's how you can diagnose and potentially resolve the issue: 1. **Check Call Logs**: Review the call logs for any

endedReason

codes, which can indicate what went wrong. You'll find these under the "Ended Reason" in your [call logs](https://dashboard.vapi.ai/calls). 2. **Identify the Issue Type**: If the issue relates to unexpected assistant behavior, here’s what you might want to check: - **Assistant Configuration**: Ensure proper configuration of settings like

timeoutSeconds

in hooks to avoid unnecessary timeouts. - **Idle Messages**: Configure idle messages to handle conversation pauses as detailed in the [Idle messages documentation](https://docs.vapi.ai/assistants/idle-messages). - **Assistant-Related Codes**: Codes like

assistant-ended-call

or

assistant-request-returned-error

could indicate specific issues in assistant logic or external APIs. 3. **Iterative Debugging**: Follow an iterative process to test changes: - After adjustments, make a test call. - Check for improvements and note any persistent issues. - Share new Call IDs and observed changes if further support is necessary. Reviewing these aspects could help resolve the issue. If problems persist, use the example report format in the [issue reporting guide](https://docs.vapi.ai/issue-reporting) to structure a detailed report for further assistance.