WRONG ASSISTANT WHEN CONCURENCY LIMIT
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.
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.
