Hello,
We observed that our concurrent request limit was 5 on April 6 at 15:15 UTC. However, we received the following error message:
“You have reached the concurrent request limit. Your limit is 100.”
Could you please check this discrepancy? Due to this issue, we are currently unable to use methods and timers, as the error continues to occur.
Thank you for your assistance.
Hello @Francis_Bagas
At first glance, the reason is not clear
We have created an internal ticket to investigate this issue.
We apologize for the inconvenience.
Regards,
Viktor
Is that app id correct?
4A47197B-AE30-FA84-FF56-0071F4010900
Hi @viktor.liablin, yes — that’s our app ID.
Hi @Francis_Bagas ,
We have an issue with analytics displaying incorrect data for concurrent requests (especially when viewing the current hour). However, in the database I can see that the limit was exceeded, which is why you were seeing those errors.
1775739240: 83
1775739300: 84
1775739360: 85
1775739420: 85
1775739480: 91
1775739540: 90
1775739600: 90
1775739660: 91
1775739720: 92
1775739780: 98
1775739840: 100 ← 13:04 UTC
Regards,
Viktor
Hi, thanks for the update!
Just to confirm—was the concurrent request limit fixed at 100, or is it something we can still increase?
The limit is fixed at that value for all applications — as far as I know, there’s no option to increase it for a specific app, but I’ll double-check and will let you know if I find out otherwise.
I’d also like to note that in the vast majority of cases, your app reaches this limit when there are some temporary server-side issues reducing request processing speed, causing unprocessed requests to accumulate until the limit is reached.
Regards,
Viktor
Thanks for the clarification!
Got it—so the limit is fixed for now.
We’ll review our side as well, particularly around request duration and any retry behavior that might be contributing to the buildup. Please do let us know if there’s any update on the possibility of increasing the limit.
Appreciate the insight!