DataStore and OrderedDataStore Operations Failing – InternalServerError

how come profile service not crashing? when datastore is doing isnt profile service using datastore

1 Like

it also does crash a bit but still manage to work

1 Like

profileservice relies on datastoreservice, its just a wrapper/library to do session locking and a bunch of other nice automated things under the hood

1 Like

Hey all, just letting you know that the engineering team has been alerted and they’re investigating :wrench:

Thanks everyone for bringing this to our attention! :slight_smile:

11 Likes

hi how come profile service not crashing like datastore?

1 Like

Why hasn’t the status site updated at all?

4 Likes

?

1 Like

ok i take that back my bad just some games that uses that is still working

1 Like

I can confirm this is also affecting live game servers. I’m unable to load data in games like rt3 when joining

status.roblox.com should definitely be updated to reflect the outage - a lot of player’s look there, see nothing, and assume that it’s an issue caused by each game’s developers which leads to confusion.

2 Likes

I’m having this error on my game as well, thanks for reporting this.


i was about to make a post about this, we had an actual jumpscare because we’re 4 days from release and i thought we just hit a bad data bug. after a few minutes of panicking and debugging i eventually replicated it in studio and got to read the actual error message

Do we have any updates regarding this? It seems all games under my group have this issue, live or not

update: the site died

I’ve come here because a friend of mine experienced this issue, thought it was his side, found this, tried my datastore, and it worked fine.

it’s random and can take several rejoins to trigger

GaG is not the reason for this 100%, if so, this would have happened ages ago, and much worse. Seems like it’s overloaded/error happened on their side.

Yep! i thought i had broken my code. it’s failing for me too

Still causing errors. Had to disable all DATASTORE till this issue has been resolved temporarily.

Yikes, but seems like only some requests fail because player data still loads after a few retry attempts