[URGENT] Concurrency limit hit
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.
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.