Assistants acting erratically, long pauses, droppe...
# support
j
Assistants are acting erratically and failing in the past hour. I see several errors in my call logs:
Call.in progress.error vapifault worker died
- CallId 019c8b45-22a4-7663-bf3d-70ec661dc61c
Call.in progress.error vapifault worker died
- CallId 019c8b54-5c6e-7ff8-a984-16879bb90f48
Phone call provider closed websocket
- CallId 019c8b59-2a4c-7116-9cf6-8837caf7b6f6
l
We're seeing some errors also @Vapi
t
Same for me @Vapi @User
p
Same here @Vapi
o
same here @User @Vapi
j
Same @Vapi Hundreds of "Ended: Call.in progress.error providerfault transport never connected", seems random (~1 out of 6 calls). Random cal lid example : 019c9f03-87b6-711d-bb02-204974db72d0
e
looking into this
c
Hi @User, I am sorry for the delayed response. The errors in the first two calls were due to an outage we had on 23rd feb, the issue has been fixed and your calls should work fine (more information about the outage here: https://status.vapi.ai/incident/831494). The third call was due to a timeout from the LLM, this appears to be a one time issue. Are you facing this issue regularly?
Hi @Jeebs from eva.be, I reviewed the call ID you shared and it looks like an issue from 11labs. On 27th, they had issues with latency (more information about it here: https://status.elevenlabs.io/incidents/01KJFNVKASGSHGEE59QQXRW7YW). It looks like the issue is fixed from their end. I highly suggest keeping fallback voices if your vapi assistants are running on production environment (https://docs.vapi.ai/voice-fallback-plan).
j
@Bharath I don't think this it. Here are many call ids today having that issue : - 019cb989-8897-7220-923e-6ab9e11577b4 - 019cb946-f6c0-7996-b589-f98cd817d055 - 019cb8e6-2ae8-7aaa-aaa4-7b586a625b53 - 019cb8be-3c2d-7220-90a8-8dc7f094c9ba - 019cb8b3-f168-7aac-b863-2a9ba79ebe42 ... and I can go on and on. Happens for weeks across assistants, but seem contained into my org 04eb8486-c2da-4500-9431-18e265dfe49e. WDYT ?
c
Hi, I reviewed the call logs and found that we are getting a lot of timeouts when sending request to 11labs,
Copy code
04 Mar, 21:19:07
šŸ”µ 15:49:05:171 ElevenLabs (WebSocket #0) Hit Unused Timeout. Closing...
04 Mar, 21:19:07
šŸ”µ 15:49:05:171 ElevenLabs (WebSocket Pool, Connection #0) Requested Eject.
04 Mar, 21:19:07
šŸ”µ 15:49:05:171 ElevenLabs (WebSocket Pool, Connection #2) Opening...
04 Mar, 21:19:07
šŸ”µ 15:49:05:171 ElevenLabs (WebSocket #2) Connecting... URL: wss://api.elevenlabs.io/v1/text-to-speech/F1toM6PcP54s45kOOAyV/stream-input?output_format=pcm_16000&optimize_streaming_latency=3&model_id=eleven_flash_v2_5&enable_logging=false&sync_alignment=true
04 Mar, 21:19:07
šŸ”µ 15:49:05:173 ElevenLabs (WebSocket #1) Hit Unused Timeout. Closing...
04 Mar, 21:19:07
šŸ”µ 15:49:05:174 ElevenLabs (WebSocket Pool, Connection #1) Requested Eject.
04 Mar, 21:19:07
šŸ”µ 15:49:05:174 ElevenLabs (WebSocket Pool, Connection #3) Opening...
04 Mar, 21:19:07
šŸ”µ 15:49:05:174 ElevenLabs (WebSocket #3) Connecting... URL: wss://api.elevenlabs.io/v1/text-to-speech/F1toM6PcP54s45kOOAyV/stream-input?output_format=pcm_16000&optimize_streaming_latency=3&model_id=eleven_flash_v2_5&enable_logging=false&sync_alignment=true
04 Mar, 21:19:07
šŸ”µ 15:49:05:221 ElevenLabs (WebSocket #0) Closed.
04 Mar, 21:19:07
šŸ”µ 15:49:05:222 ElevenLabs (WebSocket #1) Closed.
Could you try changing the voice and see whether this issue persists or not? This will help me better understand the issue you are facing.
4 Views