Since 8/28, we’ve had a huge influx of reports that many features in our games are not working (especially “search for player” mechanics like attached screenshot) due to 429 errors when Players:GetUserIdFromNameAsync() is called on the client. This often occurs starting with the first couple requests made by a player in that session. Even in studio, it’s easily reproducible after just 2-3 requests to the API.
Many features, like trading in Steal a Brainrot, are completely broken for some players as a result. It seems to potentially be only a subset of users who are affected by this issue, particularly those from outside of the US.
I can vouch for this as well. I have a moderator menu that uses Players:GetUserIdFromNameAsync() and it also started yielding a large number of these errors around that date as well. It was working perfectly fine before, and I did not change any of its code.
I myself am in the US, and this issue has been happening to me since a couple weeks ago with Players:GetUserIdFromNameAsync, as well as UserService:GetUserInfosByUserIdsAsync. I’ve had to implement many workarounds in my game in order to minimize the issue.
