My vapi assistant which trigger properly from a webhooks, sends the call to another random assistant when it reach concurency limit of 10. I didn't set any setting for that, it just push randomly to an assistant which is prompted for another thing (WHICH CAUSE PROBLEM IN THE ENTIRE ORGANIZATION). Why is that? Is it an internal bug? Can I put a setting to prevent that? I don't want to pay for an additional concurency limit. It is supposed to wait for the assistant to complete come calls, and then use the same assistant? As I said, my webhooks are properly configured, and I have no parameters/setting whatsoever to send the calls to another assistant when it reach concurency limit. Thanks for addressing this matter.

Suggestion: To prevent calls from being routed to the wrong assistant when your concurrency limit is reached, add logic in your webhook to detect when the concurrency cap is hit and return an error or a custom message. For example:

json
{ "error": "Sorry, all agents are busy. Please try again later." }

This will stop Vapi from assigning the call to another assistant and instead play your error message to the caller. [See webhook error handling](https://docs.vapi.ai/server-url/events#retrieving-assistants) Source: - [Server Events Retrieving Assistants & Error Handling](https://docs.vapi.ai/server-url/events#retrieving-assistants)

Hey, can you share the org_id? You can find it [here](https://dashboard.vapi.ai/org/settings). This will help me get more details about it.