Our org is getting notifications that we're over our limit, though we are underutilizing. Org ID is b4cf2dc7-bfc4-40d6-a0be-944655b8f13e This is popping up right as dynamic variables such as customer.number and now (for date/time) are hallucinating and failing. Please advise.

Actionable Step: Check and manually reset your concurrency counters, as desynced counters can trigger false over-limit notifications. Use the following Redis CLI command to reset the active calls counter:

redis-cli set vapi:queue:active_calls 0

After resetting, monitor if notifications persist and review your logs for any webhook or integration errors. If issues continue, please contact support with your org ID and recent log details for further investigation. (Source: internal Google Drive documentation)

Hi theschnack, To address your concern with concurrency limits, you can check the current total concurrency limit of your subscription using

Subscription.concurrencyLimit

. This includes both the default and any additional purchased limits. The breakdown is available via

Subscription.concurrencyLimitIncluded

and

Subscription.concurrencyLimitPurchased

[here](https://docs.vapi.ai/changelog/2024/11/11). If you need to track active calls, the

concurrencyCounter

has replaced

concurrencyLimit

for this purpose as of January 2025. This update doesn't change the way concurrent calls are reserved with billing add-ons. More details on the updated tracking can be found [here](https://docs.vapi.ai/changelog/2025/1/20). If you need further customization or exploration, consider the billing add-ons to increase your concurrency capacity. Feel free to check these resources and let me know if there's anything else you need.