Concurrency limits
# support
r
I'm hitting concurrency limits pretty regularly despite having fewer than 10 calls active. What is the best current way to monitor the concurrency limit? Should I just fetch all calls and filter on status to get a better sense?
v
@rowdy I'm sorry to hear you're experiencing issues with concurrency limits. To monitor your concurrency limit effectively, you can indeed fetch all active calls and filter them by status to get a real-time sense of your usage. This approach will allow you to see which calls are currently active and how close you are to reaching your concurrency limit. If you need assistance with implementing this monitoring or if you have any other questions, please don't hesitate to ask.
You can continue this conversation by mentioning me in the message.
s
@rowdy could you share your orgId so I can take a look?
r
@Shubham Bajaj orgId 395c7439-c431-4b81-b2fe-fcb781a75b38 (for my email rolsthoorn12@gmail.com)
thanks!
basically have a bunch queued and no way to process them. Is there a way I can "fake" ending the call by deleting the resource or by sending a status update from twilio?
just feels weird that a bunch of calls are staying in the queud status
s
@rowdy Just reset your concurrency limit. Make sure to add 1 second of artificial delay between each call you make/create, and the total calls in progress shouldn't be more than 10. Only create new calls after that. Most likely you have done batch calling within sub-second intervals. Give it a try and let me know how it goes. Also, you cannot reset concurrency by yourself.
r
Thanks. Will add a lock for incoming calls to make sure they're spaced. Thanks!
2 Views