[URGENT] Concurrency limit hit
# support
o
Hi Vapi Support, I’m repeatedly hitting the concurrency limit even though I’ve closed all campaigns and terminated all calls in my account. This is the third time I’ve encountered this issue, and it’s currently blocking work. Requests Please reset my concurrency counters and kill/clear any stuck or ghost calls/sessions tied to my org Context Org ID: 371ad4ed-8215-46c3-8746-a3912abd58af All campaigns are closed and all calls were ended via the dashboard, yet new calls still return a concurrency error. I don’t have Redis access Questions What is causing these ghost sessions to persist? What are your best practices to prevent this in the future (e.g., webhook handling for call end events, recommended retry/backoff, cleanup endpoints/TTL to call after disconnects)? Thanks in advance for your help and for advising on a permanent fix.
v
To immediately reset your concurrency counters and clear ghost sessions, ask your support or infrastructure team to run the following Redis command:
Copy code
redis-cli set vapi:queue:active_calls 0
This will clear any stuck sessions and allow new calls to proceed. For a permanent fix, ensure your webhook for
end-of-call-report
is reliably configured to keep counters in sync. Reference: See the troubleshooting section in the [Vapi call queue management guide](https://docs.vapi.ai/calls/call-queue-management). Source: - [Call queue management with Twilio](https://docs.vapi.ai/calls/call-queue-management)
o
I told i don't have access to redis
o
@Vapi @User @User
c
Hey Olekh, thanks for sharing your details. Our team will look into it and get back to you soon with an update.
o
i Ended all my Campaigns, but when i go inside i see that some calls are still scheduled. Thats why i got messege that i hit concurrency limit. What can i do in this situation? I want to end all of this scheduled calls. They are stuck for 4 days now all campaigns and ooutbound calls are complete or cancelled. When I try to make an outbound call via 'phone numbers'. It says im over the concurrency limit still. And i don't have access to Redis
c
Hi Olekh, Scheduled calls that remain for a long time will eventually be cleared out automatically. If you’d like to force-delete them sooner, you can do so manually using our delete API. This tool allows you to remove call IDs individually or in bulk: [Delete Calls API](https://docs.vapi.ai/api-reference/calls/delete?explorer=true) Let us know if you need guidance on using it.