For this call id 254b9ebc-d495-4fcf-b93a-4be3cb8dd38d It says silence time out in the VAPI logs, but in reality the TTS failed It tried to say "That's a really insightful" but it failed to complete sentence User was confused and call ended because of silence timeout Can we please get more detailed logs on why this failed? Was it Cartesia? Was it VAPI? Was it Claude? We want to make sure this doesn't happen again, and VAPI logs are providing no details. Thank you!

logs

🔵 17:22:52:186 Cartesia Pushing (9-0bce8cf)... 121 "That's a really insightful suggestion about how the chatbot could actively guide users to human support when appropriate." 🔵 17:22:52:977 Cartesia Pushing (9-0bce8cf)... 82 "Speaking of peer support, have you ever heard of peer support or used it yourself?" 🔵 17:22:55:730 AssemblyAI

assistant

Final Transcript : That's a really insightful. 🔵 17:22:59:905 Cartesia Message Received (9-0bce8cf). Message: { "type": "done", "context_id": "9-0bce8cf", "status_code": 200, "done": true } @danielrs18 Cartesia TTS sends us done event, then were waiting for the user's turn. This suggests an unexpected issue. If this happens frequently, consider changing providers to 11labs or Azure and share the call IDs for further analysis.

thank you for getting back to me, this is helpful it's weird that Cartesia is sending done event. we will consider using 11labs instead