I'm experiencing an "Over Concurrency Limit" error even though I don't have any active calls running. It appears some calls are stuck in a queued state and preventing new calls from being initiated. Organization ID 384294fe-47e3-456a-8577-bfada592cee6 https://cdn.discordapp.com/attachments/1359914717509849249/1359914717812101301/Screenshot_1.png?ex=67f936c6&is=67f7e546&hm=3e32a9f22ff9a46e93b4f763682d862972a0266994fbc12d469af70071039b33&

Hi there! I understand you're experiencing an "Over Concurrency Limit" error despite not having any active calls running. This can be frustrating! I can't see your specific system logs to identify exactly what's happening in your case, but I can definitely help explain what's likely happening and provide troubleshooting steps. ## What's happening The "Over Concurrency Limit" error indicates you're exceeding the maximum number of concurrent calls allowed by your current Voice API plan. Even though you don't see active calls, some calls might be stuck in the system and not properly cleared from your concurrency pool. ## Why calls get stuck According to the information I found, calls can get stuck in a queued state for several reasons: - Calls stuck in an "in-progress" state even after being hung up during ringing - Telephony provider never connecting the call (e.g., "Waited 300s But Transport Never Connected") - Improperly terminated calls that remain active in the system - Configuration issues with your assistant or SIP URI settings - Network issues or API performance problems ## How to resolve this Here are some steps you can take to resolve this issue: 1. **Check for stuck calls**: If you have access to administrative tools or dashboards, review your current call states to identify any stuck calls. Look for calls in the Vapi dashboard under logs > calls that might be in an unexpected state. 2. **Reset your concurrency limit**: This is often the quickest solution. Support can reset your concurrency limit to clear stuck calls. You've already provided your Organization ID (384294fe-47e3-456a-8577-bfada592cee6), which will be needed for this. 3. **Implement queueing and error handling**: To prevent this in the future, implement a queueing mechanism to manage calls within concurrency limits and add error handling to catch concurrency limit errors and retry after a delay.

Hey @IanMoone, your concurrency limit is already set to zero, so give it a try and let me know how it goes for you!