Hi, we have been having a few occasional call drops recently, and suspect that it might be due to concurrency issues. Is there a way to find whether we reached the concurrency limit? The call ended reason doesn't seem to have a category for this. Moreover, If a call fails due to concurrency limits, will they still appear in the call logs?

@nisalr Hello! I'm sorry to hear that you're experiencing call drops. To address your concerns: 1. To determine if you're reaching concurrency limits, you typically need to check the system or API usage metrics. VAPI might provide specific metrics or logs that can indicate when you're hitting these limits. If such a feature is available, it would be in the documentation or the dashboard where you can monitor your API usage. 2. If a call fails due to concurrency limits, it should still appear in the call logs. Most systems log all attempts to initiate a call, including those that fail due to limits being reached. This allows you to troubleshoot and understand the volume and timing of calls that contribute to reaching those limits. If you need more detailed information or assistance in checking the concurrency limits and call logs, please ask support for more info on this. They can provide specific guidance based on the exact setup and capabilities of your VAPI implementation.

You will receive an email related to it. If you touch concurrency limit.