Sudden spike in DataStore InternalServerErrors

About an hour after the release of an update to my game, Demonology, I started noticing a large influx of InternalServerErrors, with no immediate explanation as to why.


(Error report search for “InternalServerError”)


Datastore request history

I did not alter DataStores much in this update - though I did increase the size of each player’s data recently.
What might be the cause for this surge in errors?

2 Likes

As suggested by the name, this is most likely an internal server error from roblox and not your fault. However since you stated that you increased players data size you can check if it exceeds the 4MB limit (for other potential errors), now this probably won’t be an issue if your data isn’t huge but if it is I suggest checking them using #HttpService:JSONEncode(Data) and divide them into multiple keys if it exceeds 4 million.

1 Like

The absolute maximum length (max presets all maxing out the length of every preset name, every possible table item, max level, max experience, etc) is all under 10,000 characters. My data is already saved as a JSON encoded string.

I’m under the same belief that it is a Roblox issue, but it seems odd how strongly it correlates to the release of my newest update - is it possible that the amount of keys in 1 datastore negatively impacts the efficiency of all DataStores across the experience?

Hmm, afaik the amount of keys do not affect datastores, keys are loaded in using GetAsync so unless you are using ListKeysAsync() on alot of keys simultaneously it shouldn’t affect efficiency or performance.

Is the issue still ongoing right now?

This randomly resolved itself roughly 24 hours after it started - very odd that a Roblox error can harm the user experience for such a significant percentage of my player base.

I appreciate your help with this, @ALonelyGalaxy

1 Like