Concurrency limit REACHED with no active calls. He...
# supportb
Bruno
10/16/2025, 10:55 PMI made some calls to my cold contact lists that worked fine until a few numbers got stuck with the loading icon for hours, without changing. The main problem is that it says I can’t make outbound or inbound calls because it hit the concurrency limit — but there are no active calls! I’ve checked everything.
I use Vapi through the web interface, via the dashboard.
My ORG ID: fc55922b-3a49-4981-91f8-970f9f6a84a8
https://cdn.discordapp.com/attachments/1428516817055383612/1428516817697243263/image.png?ex=69413ab5&is=693fe935&hm=05cd3e376337fbd8473ab6e590317743d214ef147c585172bfb03ea22601664a&
v
Vapi Support Bot
10/16/2025, 10:57 PMActionable Step:
This issue often happens when the concurrency counter in Redis gets out of sync, blocking new calls even if none are active. If you have access to your Redis instance, run the following command to reset the active calls counter:
Copy code
redis-cli set vapi:queue:active_calls 0b
Bruno
10/16/2025, 10:58 PMI do not have access to Redis. Please Help Vapi support
Bruno
10/16/2025, 11:00 PM@User
Bruno
10/16/2025, 11:01 PM@Aditya
Bruno
10/17/2025, 1:50 PM@User
v
victor
10/18/2025, 8:31 AMi got the same problem
b
Bruno
10/20/2025, 2:15 PMHow do you fix???
Bruno
10/20/2025, 5:37 PM@User I need Help
Bruno
10/20/2025, 5:48 PM@Vapi Support Bot I'm using VAPI's standard managed service for simple outbound campaigns. Building a custom queue management server is way beyond the scope of what I need and what your platform advertises.
Your built-in queue management should handle this. If there's a platform-wide bug preventing basic outbound calling, that's something your team needs to fix on the backend, not something customers should have to engineer around.
If this can't be resolved within 24 hours, I'll need to switch to a competitor platform.
Please escalate to engineering
v
Vapi Support Bot
10/20/2025, 5:49 PMThank you for providing your Org ID and details.
Your issue has been escalated to Vapi engineering for urgent review, as this concurrency lock requires backend intervention for standard managed service users. No further action is needed on your end—Vapi support will reset your concurrency counter and follow up as soon as possible.
If you do not receive a resolution within 24 hours, please reply here to request an update.
Source:
- [Vapi Internal Documentation Concurrency and Support Escalation](https://docs.google.com/document/d/1X1UzOVUrma47typ4RnohwConQu9gH26iYz9wpZvDXO0/edit?usp=drivesdk)
c
Chiranjeet Mishra
10/20/2025, 9:59 PMYour concurrency has been reset. Let us know if you encounter this issue again
b
Bruno
10/21/2025, 2:24 PMKyle, my Concurrence Time was reset, and I managed to launch another Outbound Call campaign. However, it entered an infinite loop again and isn’t finishing the campaign. The phone numbers included in the campaign did receive the calls, but the campaign never ends — so I can’t start another one, even though I still have over 300 numbers to call.
* ORG ID: fc55922b-3a49-4981-91f8-970f9f6a84a8
* Campaign ID: e24f7ce2-ec7c-4ebf-b60a-33499c8fc765
Bruno
10/21/2025, 2:25 PM@Vapi Incident @User @Vapi Support Bot @Vapi
v
Vapi Support Bot
10/21/2025, 2:27 PMAction Required:
Since your outbound campaign is stuck in an infinite loop and blocking new campaigns, please provide the stuck campaign's ID and your Org ID to Vapi support (which you have already done). The next step is to request that Vapi engineering manually reset or terminate the problematic campaign from the backend, as this cannot be resolved from the dashboard.
If you do not receive a resolution within 24 hours, reply here to escalate the issue again.
(Source: Vapi Outbound Campaigns documentation and escalation procedures)
b
Bruno
10/21/2025, 2:32 PMSo please, request Vapi engineering manually reset or terminate the problematic campaign from the backend
3 Views