While attempting to test scalability of my application I ran into a concurrency error (its been giving me this error for around 24 hours). Although the calls have ended i'm still receiving this error any idea how to resolve this? Also I was wondering what the concurrency limit is and how I can increase it. https://cdn.discordapp.com/attachments/1307820439795662848/1307820440298848267/image.png?ex=673bb233&is=673a60b3&hm=ea6f4c660067e7d8f921a07771a3f8cb777b07ef47fe07cdcda3c4911a4b1ef8&

@Adam12234 I'm sorry to hear that you're experiencing a concurrency error. It's possible that the error is persisting due to a temporary issue or a glitch that has caused the system to not properly reset after your scalability tests. To resolve the concurrency error, I would recommend the following steps: 1. Ensure that there are no ongoing processes that might be contributing to the concurrency limit. 2. Restart your application or the services that are responsible for handling the voice API calls, if possible. 3. Check the system logs or error messages for any additional information that might help identify the cause of the issue. Regarding the concurrency limit, the specific limit can vary based on the service provider and the plan you are subscribed to. To find out the exact concurrency limit for your application and how to increase it, you would typically need to refer to the documentation provided by the service or contact their support team directly. If you need assistance with contacting support or if there's anything else I can help you with, please let me know. If the issue persists and you're unable to resolve it, reaching out to the support team for your voice API service would be the best course of action. They can provide more detailed information on concurrency limits and how to adjust them according to your needs.

Hey @Adam12234 , could you send me your org_id which you're experiencing issues with? You may increase your concurrrency limit by purchasing more through the billing page

@User Sorry for the late response but here is my org_id : 35641eb6-767c-4752-bc17-b06176e976b5

Hey @Adam12234 please give it a shot now

Awesome, thank you! its up and running. what exactly went wrong was it an error on our end causing the 24 hour error or from Vapi? and how can we prevent/fix this in the future? @bryant

Hey, I believe it was a database error on our end which caused this, so it shouldn't occur again @Adam12234 . Please let us know if it does and apologies for the trouble

Thank you, you've been super helpful!