Hi Vapi team, My organisation (ID above) is currently unable to make any outbound calls or run campaigns. • We receive the error “Over Concurrency Limit” for every call attempt (even 1-off test calls) despite no active calls for 12+ hours. • Campaigns remain in “Scheduled” state (IDs: 3dfde99b-2196-433e-a911-c9c20d3813aa; 1886d76b-966f-4e46-9c3e-a6b752187df4; 3906f9f8-69ad-4f76-b836-a4159c4e417b) and never execute. • We purchased an additional concurrency lane but issue persists and system appears unusable. • We’ve confirmed in UI / logs / external app that no calls are currently running. Request: Please reset our concurrency counter / queue state for this organisation so we can resume outbound calls. Also please verify our current concurrency limit and free lanes status.

Action Required: This issue requires immediate escalation to the Vapi engineering team, as persistent "Over Concurrency Limit" errors with no active calls usually indicate a system-level counter desync. Please open a support ticket and include your Org ID, campaign IDs, and a summary of the problem. The Vapi team will need to reset your concurrency counters and queue state to restore outbound calling. Reference: [Vapi documentation on concurrency issues and escalation](https://docs.vapi.ai/calls/call-queue-management#implement-queue-management-server). Source: - [Call queue management with Twilio](https://docs.vapi.ai/calls/call-queue-management#implement-queue-management-server)

Message marked as helpful by @developer solarfast! 🎉

Hi Krzysztof, For managing concurrent call issues, we've updated our concurrency tracking mechanism. Now, instead of using

concurrencyLimit

, we track active calls with a new field

concurrencyCounter

. This change ensures more accurate tracking of your call activities, and it should help resolve the issue you've experienced with concurrency limits when no active calls are present. If you want to review or adjust your concurrency settings, refer to the billing section on our [dashboard](https://dashboard.vapi.ai/org/billing/add-ons) for any related add-ons or configurations. For further technical details, you can check the [changelog for January 20, 2025](https://docs.vapi.ai/changelog/2025/1/20). If you're still encountering problems related to concurrency limits or how they're being calculated, feel free to give these resources a look for potential insights or solutions.

I've tried those but the campaign is stuck once again. c9fa52e3-5bf7-40b7-b71e-993c9663c3eb it wont do any calls and there havent been any calls made for over 24hrs (concurrency error persisting)