we are unable to trigger a call or schedule due to hitting the concurrency limit. This is despite the fact that we have removed all scheduled calls, and yet the issue persists. Given that we are running a scaled business, this limitation is significantly impacting our operations. We kindly request your assistance in investigating this matter and would also like to explore the possibility of elevating the concurrency level to better accommodate our needs. https://cdn.discordapp.com/attachments/1424720979476742265/1424720979774410763/image.png?ex=68e4fa4f&is=68e3a8cf&hm=53c4c0d9549f60dadc0e88ebea6cf6a9cc4150fe90635e6b0f200d91efb4763c& https://cdn.discordapp.com/attachments/1424720979476742265/1424720980227653652/image.png?ex=68e4fa4f&is=68e3a8cf&hm=30c4898a7914187462d07c05520e33825c88f163f8915687b7d5f7d71dfc72b6&

To increase your concurrency limit and resolve the "Over Concurrency Limit" error, go to your [Vapi billing page](https://dashboard.vapi.ai/org/billing), click "Switch to Credit Based Billing", and select the desired concurrency add-on. This will let you scale your concurrent calls as needed. Note: This change requires manual action in the dashboard and cannot be reverted to the old billing system. For more details, see the [Vapi changelog](https://docs.vapi.ai/changelog/2024/10/10). Source: - [Changelog October 10, 2024](https://docs.vapi.ai/changelog/2024/10/10)

The issue is not that as we don't want to increase it right now we just want this issue to go away we already got this, the issue is that why it's saying "Over Concurrency Limit" while there is no ongoing call or scheduled call !!

I can help you check why the concurrency flag isn’t resetting even with no active or scheduled calls. It’s likely a stale session or pending job still counted in the system. Can you confirm if you’ve inspected active sessions or API logs for lingering instances? Once we identify that, I can guide you on safely clearing the concurrency state. @_.lof

yes @Vercel i have inspected active sessions it's API logs

Thanks for confirming. This usually happens when the concurrency state remains locked due to an unclosed session or incomplete cleanup in the backend queue. We can directly assist by identifying and clearing the stale concurrency keys or cached sessions from the system to restore normal call scheduling. Let’s move this discussion privately so we can access the needed details and resolve it safely. @_.lof

thanks for this message okay, I ve sent you privately @Vercel