Urgent: Bug in Concurrency Systems

I'd request your urgent help to this matter, our systems are scaling fast (and in Production) and Vapi APIs are responding in a very unreliable manner.

Hi Team,

We have a system with following properties

  1. We have got 5 numbers where each number handles one call at a time. (We have limitation of one active call at a time from number provider)
  2. A number is marked busy when a call request is sent to Vapi
  3. A number is freed up and ready to accept calls again when we receive status ended from Vapi Webhook
We still receive concurrency limits errors a lot of time. (even though we should never considering Vapi default concurrency limit is 10)

For an instance,

On 24 Nov 2025, at 4:43 PM - 4:44 PM (IST), there are 10 calls which are showing in Vapi call logs which were all customer busy or customer did not answer

Still, all the calls between 4:44 PM - 4:48 PM failed with concurrency limits hit error. (there are no call logs between this duration in Vapi signifying that system was free during this time)

It seems that Vapi doesn't free up concurrency sometimes even when there are no active calls going on.

Thanks,
Karun
Was this page helpful?