Getting meeting ended error in frontend when custo...
# supportm
Mehul
04/29/2025, 12:40 PMDuring the call if the customer asks the assistant to end the call, and assistant properly ends the call saying the end call phrase, even then the web sdk emits an error event:
{
"action": "error",
"errorMsg": "Meeting has ended",
"error": {
"type": "ejected",
"msg": "Meeting has ended"
},
}
What's the correct way to handle this? Or is it some bug. We don't see this when the call goes through the full flow and then ends with "assistant said end call phrase".
k
Kings_bigđź’«
04/29/2025, 2:38 PMThe SDK emits an “ejected” error, which you can safely treat as a normal call end in your handler logic.
m
Mehul
04/29/2025, 2:43 PMOh cool. Thanks much, I can patch that quickly. Is this reliable and the correct way to do it?
Mehul
04/29/2025, 3:02 PMCan there be any case where an actual error in the backend or something can lead to SDK emitting an “ejected” error?
Mehul
04/29/2025, 3:09 PMAnd is it possible to get a list of error types/ messages and when are they emitted?
k
Kings_bigđź’«
04/29/2025, 3:32 PMYes
m
Mehul
04/29/2025, 4:17 PMYes to what exactly?
Mehul
04/29/2025, 4:34 PM@Kings_bigđź’«
1. Can there be any case where an actual error in the backend or something can lead to SDK emitting an “ejected” error?
2. And is it possible to get a list of error types/ messages and when are they emitted? If so can you please direct me.
It has become a big issue, need to resolve asap. Please help.
k
Kings_bigđź’«
04/29/2025, 9:33 PMYes, a backend issue (like assistant errors or misconfigurations) can cause the Vapi SDK to emit an “ejected” error; you can find all possible error types and when they’re triggered in the [Vapi call ended reasons documentation](https://docs.vapi.ai/calls/call-ended-reason), which outlines causes like assistant-error, pipeline-error, or assistant-not-found.
3 Views