ELEVEN LABS EXCEEDED ERROR
# support
h
Hi, Pipeline error eleven labs voice failed" ElevenLabs message error: "Maximum simultaneous contexts per WebSocket connection exceeded (5). Please close an existing context before opening a new one." This is the callID: 019d1f57-d8b4-7bb3-b13f-2aff8d2b0829 Note: We are using VAPI Api (Not ElevenLabs). Thanks!
a
This error usually happens when too many concurrent voice contexts are open on the ElevenLabs endpoint via VAPI. To fix it, make sure to close or reuse existing contexts before creating new ones. I can help implement a proper context management solution to prevent this from happening again. @heisenberg
h
do we even get to configure that, we only give the provider name and vapi opens/closes the connections right? @Vapi Incident @Vapi @User
a
You’re right that VAPI handles most of the connection lifecycle internally, but in practice this error usually comes from how sessions/requests are triggered on our side. If multiple calls or events try to open new contexts too quickly without reusing the same session, it can hit that limit. So while we don’t directly control ElevenLabs connections, we can still prevent it by adjusting how we manage call flow, concurrency, and reuse within VAPI. I can take a look and help optimize that so it stops happening. @heisenberg
h
@User please reply — I see abosolutely no support for the tickets raised from our end. not sure why is this never reaching out to you folks
e
Hey! Our team usually responds in 1-2 days, but I've flagged this for them!
s
Hey@heisenberg, will take a look, for now please add an 11labs voice as a fallback voice in your assistant, this will prevent calls from dropping the call, you can set it from assistant setting.
h
We are restricted to 11labs as we have cloned a certain tone of the voice we needed. we cannot add it as a fallback as that's the only provider we can use @Sarthak ( Vapi )
s
Hey, I understand your concern. I am on it right now, will inform you about updates.
Looks like this issue is not happening now; the last instance was on 24th March. Can you ping me if this happens again?
h
sure, Can I know the reason why it has happened?
s
Tbh I am not sure, but it was due to a higher number of contexts created than 11labs allows per websocket connection. For better stability, you can switch to the weekly channel.