over concurrency limit
# support
m
Hi, am having an issue with my automation where it says overconcurrency limit reached. This is the last caller ID: 0c77a181-ef9c-44d5-85c4-17b489ae46e7 At times it gives a 201 status and no call goes through. Please help.
a
HeyMatilda Thank you for creating the ticket! A member of our team will reach out to you shortly.
v
@Matilda Hello! It sounds like you're encountering an issue with overconcurrency, which means that you're trying to make more simultaneous requests than your current plan allows. Additionally, receiving a 201 status code indicates that your request has been accepted, but it doesn't necessarily mean the call has been initiated successfully. To assist you better, I'll need to check the details of the error you're experiencing. Could you please provide me with the exact error message or code you're receiving? This will help me identify the specific problem and guide you on how to resolve it.
You can continue this conversation by mentioning me in the message.
m
Over Concurrency Limit. error Bad Request statusCode 400
v
@Matilda Thank you for providing the error details. The "Over Concurrency Limit" error with a 400 Bad Request status code indicates that you are exceeding the maximum number of concurrent calls allowed by your current Voice API plan. To resolve this issue, you can consider the following options: 1. **Review Current Usage**: Check your application to ensure that it's not making more simultaneous calls than your plan permits. Look for any loops or concurrent processes that might be initiating more calls than expected. 2. **Upgrade Your Plan**: If your usage legitimately requires more concurrency, you might need to upgrade your Voice API plan to accommodate the higher concurrency needs. 3. **Implement Queueing**: If upgrading is not an immediate option, you can implement a queueing mechanism in your application. This will manage the calls and ensure that they are initiated within the concurrency limits. 4. **Error Handling**: Improve error handling in your application to catch this specific error and retry the call after a delay, ensuring that you stay within the concurrency limits. If you need further assistance with reviewing your current usage or exploring plan upgrades, please let me know, and I can guide you through the next steps. If you're ready to close this support ticket, just let me know, and I'll proceed with that as well.
m
The problem is that the first time I got this error was a few days ago, but ever since i still get the error message even when I had turned off my automation for a day or two. It's only one call so the error doesn't even make sense
v
@Matilda I understand how that can be confusing. If you're still receiving the "Over Concurrency Limit" error even after ensuring that no multiple calls are being made, there might be an issue that needs further investigation. Here's what we can do: 1. **Check Account Status**: Verify that your account status is in good standing and that there are no issues or blocks that might be causing this error. 2. **Review API Logs**: Look into the API logs for the time periods when you received these errors. This can provide more insight into what might be causing the issue. 3. **Contact Support**: Since the error persists even after you've turned off your automation, it might be best to reach out to the Voice API support team with the details of the error, including the caller ID you've provided and the times you've experienced the issue. Would you like me to help you with any of these steps, or is there anything else I can assist you with?
m
@Shubham Bajaj Please help
Please help resolve this issue
v
@Matilda I'm here to help you resolve this issue. Since the problem persists even when your automation is turned off, we need to take a closer look at your account and system logs to understand what's happening. I will initiate a review of your account status and API logs based on the caller ID you provided. This will help us identify any anomalies or persistent issues that could be causing the "Over Concurrency Limit" error. Please bear with me for a moment while I perform this check. If any further action is required on your part, I will let you know. If the issue is on our end, rest assured that we will work diligently to resolve it as quickly as possible. If you have any additional information or have made any recent changes to your account or automation setup that might be relevant, please share them with me now.
m
I meant that even when i try to turn the automation on, no calls go through because it gives the over concurrency limit error. which doesnt make sense because there were no simultaneous calls being made.
v
@Matilda I understand the situation better now. It seems there might be a discrepancy in the system that's incorrectly flagging your single call as exceeding concurrency limits. To address this, we need to perform a detailed investigation into your account and the specific call attempts. Here's what I will do: 1. **Review the Caller ID**: I will check the system for any issues related to the caller ID you provided to see if there's a specific problem with that call. 2. **Audit Account Concurrency**: I will audit your account to ensure that the concurrency limits are set correctly and that there are no errors causing this issue. 3. **System Check**: I will also perform a system check to rule out any glitches or bugs that might be causing the system to incorrectly report concurrency issues. Please allow me some time to conduct this review. I will update you as soon as I have more information. Your patience is appreciated while we work to resolve this issue. If there's anything else you can provide that might help with the investigation, please let me know.
m
Okay, I'll wait for your feedback
v
@Matilda Thank you for your patience. I will proceed with the necessary checks and get back to you with an update as soon as possible. Rest assured, we are committed to resolving this issue for you promptly. If you have any further questions or concerns in the meantime, please don't hesitate to reach out. I'm here to help!
s
@Matilda can you try again I have reset your concurrency limit.
m
Hi, I just tried and i got a 201 status code. Call ID:470eddef-d100-4307-b2c7-a4c48a379b58 ...The logs say no assistant assigned but i did/have assigned a squad to that number
s
@Matilda can you try again your concurrency limit has been reset!!
m
still getting a 201 status code (id 623f05ee-039c-4eec-befc-c670dd22d961 phoneNumberId 4201137c-c2c8-4234-9f03-def77c4160cf type outboundPhoneCall createdAt January 29, 2025 7:38 PM updatedAt January 29, 2025 7:38 PM orgId a7525429-5c9a-42fa-8478-9baeb3a4cf80) No call came through
s
@Matilda Try again now your organization concurrency limit has been rreset.
m
Thank You 🙂
4 Views