We've hit the concurrency limit AGAIN with no active calls. We've raised this multiple times with NO response. Our Org ID is fa3549c9-cea8-439c-9cf1-4643c64857c0 Please tell me that 1) we'll actually get a response and resolution this time and 2) this is being addressed globally. This issue is appearing repeatedly on discord and all of the solutions seem to be one off. @User where is the support on this and just support in general?

Hi JakeLease, If you are experiencing issues related to concurrency limits, it's worth noting the recent updates to Subscription's concurrency tracking. As of January 20, 2025, the concurrency limits in your subscriptions now track active calls with

concurrencyCounter

instead of

concurrencyLimit

. For further information on managing your subscription and understanding concurrency limits, please refer to [this document](https://api.vapi.ai/api/). Additionally, ensure that your subscription includes the necessary concurrency capabilities, especially for enterprise plans, by using the

Subscription.concurrencyLimitIncluded

for default limits and

Subscription.concurrencyLimitPurchased

for any additional purchased limits. You can also monitor the minutes used in a subscription with

Subscription.minutesUsed

. If you have recently purchased additional concurrency limits and are still facing issues, double-check if these purchases are properly reflected in your subscription settings.

I'm not seeing the references to the concurrencyCounter in the swagger doc. We are not on enterprise now, although I've been trying to get a call setup with Sales. Our subscription indicates the additional lines that we purchased when this issue began to appear last week.

The counter is in our backend and is not publicly accessible. This issue is currently being worked on by our team so if you run into concurrency issues just let us know and we will manually reset it on our end.