Roblox Studio continously says "Number of requests exceeded limit" when attempting to use plugins that use HTTPService

Whenever attempting to use a plugin that uses HTTPService (such as Rojo), Roblox Studio completely rejects sending the request, claiming “Number of requests exceeded limit”.
This happens for every single plugin I attempt to use. I can only mitigate it for a very short period of time by reloading the place in Studio.
This includes requests to LocalHost (127.0.0.1), not just Roblox.
Video below demonstrates me attempting to use 3 seperate plugins that use HTTPService.

Expected behavior

Any plugins that make requests to LocalHost using HTTPService shouldn’t have any ratelimiting whatsoever, and requests to Roblox’s APIs shouldn’t be ratelimited constantly.

1 Like

Hi, thanks for the report.

Could you provide me with some more information? Could you please send me your universe/placeIds. Is this something recent you have noticed, or has it always occurred?

Thanks!

Hi! It’s currently occuring in Experience 5592014843 (Place 16191936891), and it’s happened for months now. I usually worked around it by reloading the place, but it has gotten to a point that I can’t ignore anymore. Thanks!

Hi, last year we increased the limits

5 parallel requests for plugins and 8 for user scripts in Studio.

Are you sure you are not hitting these limits? It might be helpful if you could try to track how many requests your plugins are sending. Plugins like Rojo will take one of these parallel requests indefinitely, I believe, and if you have multiple plugins doing this, you may be running out of limits.

I disabled all of my plugins except for the one I’m trying to use, yet its still saying I have exceeded limits

Hi, checking back in on this. Aside from the parallel request limits, there is an overall throttling of 500 requests per minute. This limit is shared between plugin and non-plugin requests.

I see you’ve disabled other plugins, but are your scripts making any HTTP requests that could cause you to hit this limit?

A separate request limit for plugins is a good idea, and something we can look into.

Hello!

I’ve noticed this too recently (couple days ago). I eventually noticed I’d get 429 error code when testing my feedback system. There is no other request done by the game otherwise (in studio test atleast)

I also use Rojo and iirc it happened while I had it connected to vscode

Experience: 805217647, Place: 2310273786

Hope this can help!

* Side note:
I’ll start by saying that for this part I have no idea what the error code is, so it might or might not be related. I remembered it while writing this, but some of my staff members are complaining that sometimes the activity logger is not sending their log from the actual game. The activity logger makes maybe between 2-3 requests per day. I also have a feedback system which is used more often, but it’s also not making many requests, maybe 3-4 requests per day (Experience: 508099649, Place: 1251631024)

Hi Sylmat, really appreciate your input!

A 429 response code looks like the request are making it through HttpService limits, but the server you’re trying to hit is doing some rate limiting on its own end. Could that be what you’re seeing?

Thank you!

2 Likes

Ohhh right maybe.. I use a Cloudflare worker as proxy and it doesn’t report any errors. But looking at how I did it, I believe they would be suppressed/ignored as it just forward the request and return the response.. I’ll make it throw errors explicitly and check back in couple of days.

It’s also pretty vague in my mind because I didn’t think anything about it at the time (so I might be wrong), but iirc the error was specific to the place/studio. It still worked in the main game (a different experience)

Hello!

After looking further on my part, it is most likely unrelated, sorry. With the added logging I noticed that there was a way for the client to spam requests in very specific conditions.

Have a nice day!

Turns out, disabling the plugins didn’t work, I had to fully uninstall them from studio. Now I no longer have issues with http limits