nicko
10/16/2025, 6:01 PMVapi Support Bot
10/16/2025, 6:02 PMbash
curl https://your-server.com/health
If you see nonzero activeCalls or callsInQueue, you may need to reset your counters or investigate stuck calls. This often resolves "over concurrency limit" errors even when no campaigns appear active ([Vapi docs](https://docs.vapi.ai/calls/call-queue-management)).
Source:
- [Call queue management with Twilio](https://docs.vapi.ai/calls/call-queue-management)nicko
10/16/2025, 6:17 PMVapi Support Bot
10/16/2025, 6:18 PMbash
redis-cli set vapi:queue:active_calls 0
This will manually reset the active calls counter, which should resolve "over concurrency limit" errors if no calls are actually running. Make sure you have access to your Redis server before running this command.
For more details, see the [Vapi call queue management docs](https://docs.vapi.ai/calls/call-queue-management).
Source:
- [Call queue management with Twilio](https://docs.vapi.ai/calls/call-queue-management)nicko
10/16/2025, 6:23 PMVapi Support Bot
10/16/2025, 6:24 PMnicko
10/17/2025, 12:27 AMChiranjeet Mishra
10/22/2025, 4:37 PMSubscription.concurrencyLimit property. This shows both the included and any additional purchased limits. You can access individual parts with Subscription.concurrencyLimitIncluded for the default limit and Subscription.concurrencyLimitPurchased for any extra purchased capacity. For more details, you may refer to the [Subscription schema](https://api.vapi.ai/api/).
Additionally, note that the tracking of active calls is now done with concurrencyCounter which has replaced the old method used for this purpose, without affecting the reservation process for concurrent calls.