Losing players & Game breaking because of Roblox MemoryStore failures

Hey, I’m owner of an Active Roblox Game.

We have a datastore system that relies of MemoryStore for session-locking, and when Roblox’s MemoryStore started failing here’s what happened:

  • All our players got kicked out of the game.
  • Then they tried to rejoin all at once pretty much, and when the memorystore started getting used, it started throwing errors, so after 5 failed attempts of the session-locking due to our session-lock design, it started kicking them out. We ended up losing all our players and they couldn’t rejoin either because they kept getting kicked out due to this.

MemoryDataStore Documentation also turned out to be nothing, but a lie:


As you can see in the documentation, that’s what they claim is their limits. But when hundreds of players started joining at once, it suffered from ‘ratelimits’, which wasn’t supposed to happen and there’s nothing wrong in our code to cause excessive calls. Instead, this is the result of what looks like Roblox registers ccu too late to take into account for memorystore, so when they joined all at once, it was still thinking we had around 0 ccu, instead of hundreds. Ending up with all players getting kicked out.

It wasn’t until dozens of minutes later, it starts throwing Internal Error, Unknown Error. (the error it was supposed to throw instead, before)




Another thing that happened, when this started unfolding, I quickly joined studio and rushed to edit the datastore to disable the session-locking, the script I supposedly had edited, turned out not to be the script that was actually edited. Studio got corrupted, and instead of editing the script that I was editing, it edited another script. Ended up breaking our whole game. This didn’t happen once, but 3 times in about 10 minutes.

Also, as a result of us disabling the session-lock later, several users could’ve suffered from data corruption / data loss.

We’d like to get compensated by Roblox for this aswell.

1 Like

Thanks for the report. We had issues with memory stores earlier today (September 6, 2025, from 13:23 PDT to 14:31 PDT), which have now been resolved.

I know about the memory store issues, however, the rate-limit wasn’t supposed to happen. Not only that, the Studio bug when editing a script, and it editing another script is something that should be fixed. Is there also any compensation?

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.