Assistant stopped for no reason (repeat)
# support
s
Thanks for the prior answer but it was wrong. The agent stopped talking five times during the call. (I already knew about the call total time limit.) It kept stopping again last night. Prior ticket: The assistant stopped talking 5x+ in my last call with ID 25f2be2b-a2ab-4a7d-a5ee-f422343b6174. Please can you look into it? thanks.
v
message has been deleted
@Stephenm I'm sorry to hear that you experienced interruptions during your call. To assist you better, I will need to investigate the issue with the call ID you provided. Please give me a moment to look into this for you. In the meantime, could you please let me know if there were any error messages displayed or if you noticed any patterns when the assistant stopped talking? This information could be very helpful in diagnosing the problem.
You can continue this conversation by mentioning me in the message.
s
@User the 'Ask for help' button fails for me. Pls help? thx
@Sahil please repoen yesterday's ticket? thx
s
can you send me the timestamp in recording
when this issue occured
s
@Stephenm share the timestamp really required.
s
LLM stops talking at 22 seconds on this call ID 80399b83-0545-4727-9773-2e51d9f533c8
This was a new call, and a demo to a client. You can hear the client saying "Quite buggy" after that.
LLM stops again at 53 sec on call ID 9697d5f5-defb-4bbc-9574-a268c1cb0f30. Again this is a client demo.
This is happening a lot. We cannot do demos to clients like this, let alone go to production.
Please help urgently.
this is happeneing every call with different assistants
@Sahil @Shubham Bajaj
bump
bump
s
@Stephenm looking at it.
@Stephenm can you try other voice providers because cartesia is not voicing out.
logs
- LLM giving output but TTS Buffer cartesia was not ready - Time from LLM request to start token was 2552ms
Let Me Know How it Goes.
s
Thanks @Shubham Bajaj for looking into, much apprecaited. I am AFK and will retest later. However, this happened with 11labs on call 25f2be2b-a2ab-4a7d-a5ee-f422343b6174 at 1m26se and 2m55s and 3m33s and 5m13s and 5m56s and 6m16s This is a wider issue, affecting other voice providers. Please could you look into that? thanks
+ @Krishna
s
@Stephenm i am also AFK from keyboard will look into in sometime.
s
ok. just so you know and hopefully find feedback useful, we now looking at porting to another provider in case of vapi quality issues.
s
logs
šŸ”µ 09:37:46:473 Voice Input Formatted: " . 5. You'll be taken to a listing page where you can set", Original: " 5. You'll be taken to a listing page where you can set" šŸ”µ 09:38:03:861
assistant
Final Transcript : You'll be taken to a listing page where you can set.: 0.7531738 šŸ”µ 09:38:13:647 Idle Timeout Triggered But No Idle Message. šŸ”µ 09:38:33:861 Silence Timed Out. Ending Call... https://cdn.discordapp.com/attachments/1283318271260626985/1284531785358639217/Screenshot_2024-09-14_at_8.39.00_PM.png?ex=66e6f8f3&is=66e5a773&hm=99387ce9ae71d93f661315dbb90a515397e690009f3fc0020959a6d54d849d26&
@Stephenm As you can see in the logs, the model outputted
5
at the end and stopped. Because this was perceived as a continuation of the conversation, the call ended in silence while waiting for further assistant responses. The same thing happened with other calls.
s
@Shubham Bajaj Thanks for looking into this (apologies I was away). So are you saying the LLM stopped yielding text. Probably we need a work-around. Maybe we use the 'hang' server message update then inject a call control to say 'please continue' to the client or lLM?
s
try if this works, instead check within your prompt what's causing these LLM generated responses.
2 Views