Assets don't load in local server test due to error 429

When I run a local server test for a large place, hardly anything in the place loads and the output shows almost all assets/textures failing to load due to “Error: HTTP 429 (Too Many Requests)”. Studio never retries loading them, so it’s permanent in the session and makes it near impossible to do anything inside of the server test. Characters, UI images, meshes, textures. animations all do not load. I did try uninstalling and reinstalling studio multiple times, as well as clearing all the temp files, it did not fix the issue. This does not occur in the server window, and different clients don’t experience it equally, some load more or less than others. The beta features I have enabled are: Visualizing UGC Validation, Video Uploads, Texture Generator, Solid Modeling On Meshes, Segment by Parts, Script Sync, Revamped Asset Manager, Remote Breakpoints, Playtest Agent, Party Simulator, New Video API, New Studio Camera Controls, Live Animation Creator, glTF Export, Face Capture.

System Info
OS: Win 11
CPU: AMD Ryzen 7 7700X
Memory: 32 GB DDR5
Disk: Samsung SSD 990 PRO 2TB
GPU: NVIDIA GeForce RTX 4070 SUPER

Expected behavior

I expect all assets to all load immediately or within a minute of launching the server.

A private message is associated with this bug report

1 Like

Bump! The same exact issue has been happening to me for weeks now

Hi @entoural!

Could you specify which API calls caused the 429 errors and/or provide with captured logs? That would be helpful to figure out why it rejects the requests from Studio. Thanks!

Additionally, how large is the place? How many instances are in ReplicatedFirst, ReplicatedStorage, and StarterPlayer? How many different asset IDs are trying to load on launch?

Hello, I have a post detailing a video and my logs with the same issue:

The place is large, with 64k instances in those containers and over 8k unique asset IDs

Hi entoural, can you try logging out and back in on Studio per Error 429 Halting Ability To Develop - #3 by TheBobo88 to see if this mitigates the issue? We’re still investigating on our end.

Thank you.