Datastore Problem - HTTP 500 (Internal Server Error)

[1billybob1]

Hello,

ISSUE

I’ve once had this issue back in October, but it seems like it has returned. Last time the issue occurred, it was an issue on ROBLOX’s end.

This issue has begun occurring again around mid-day EST in my game. It has gotten prevalent enough where I have had to temporarily close off my game.

Every server in my game (that holds about 22 players each) is breaking completely. After receiving enough reports, I’ve investigated a server and found the following error logs:

I have not made any changes to my game in over 2 months, and just today it began throwing this error and has been breaking in every server. Here is the current error I’m getting:

The first notable error is the ‘Script timeout: exhausted allowed execution time’. This code has been working flawlessly since November of 2019 and has never thrown this error before. It just began throwing this error today. So I do believe this is related to the overall problem.

And of course, below, is the 502 error, as well as the HTTP 500 (Internal Server Error).

It began happening today, and I began receiving an influx of bug and broken server reports around 4:15 PM EST

REPRODUCTION

I’ve tested my game a lot by myself while it has been temporarily shut down, and have had no issues. It only seems to happen with many users in a server. When there’s a full server, it doesn’t take long for the server to completely break and throw this error. It is also not only related to DataStore2, as other aspects of my game that use the normal Datastore are giving the same error. I also do believe that the ‘Script Timeout’ error is related to this issue, because as stated, it’s never occurred before until today when the issues were being reported.

This issue has happened before (the HTTP 500 error, not the script timeout error), and I’ve posted an article back then here: DataStore Issue - HTTP 500 (Internal Server Error). I reposted this because if it’s affecting me, I’m sure it may be affecting others, and it may be game-breaking for others as well. So I believe it is urgent enough to create a brand new thread for this problem.

If anyone else is experiencing a similar issue in their experiences beginning recently, please leave them here.

Thank you for reading.

[Azorpine606 (azor)]

Very strange and serious bug. I sincerely hope this is fixed soon, as I am an avid Tornado Alley Ultimate fan myself, and am a developer who is working on a game using multiple datastores, meaning that if this is an issue affecting multiple games, it may affect my game as well. This may be on ROBLOX’s end again, but we can never be sure. This bug is very serious. I hope the best for your game, and hope this is fixed soon so it may return.

[crowsegg]

hi, Can you please provide your universe id, placeid for the game ? We will look into it.

[1billybob1]

Hi!

The universe ID is 806257808
The place ID is 2313058949

I greatly appreciate the staff taking the time to look into this. Thank you tremendously!

[PlanetCaravn]

Hello I have also gotten this error several times now.

When I first released my game last Friday(7/2/21) I just got warning (Seen in image below). When testing with my partner, we never had any problems.
However, We had 100+ people join the game when we first released. They start in the lobby, from there we teleport 24 players to a match. This is where we ran into issues

When players kept not being able to spawn in we closed the experience and set up a separate testing environment. Here we kept it private, just testing with members who had joined our community.
We kept getting the warning with people failing to spawn into match (place where players are teleported)

It wasnt until today and yesterday that we started to get these errors:

As seen these are the same errors as the OP, and we are using the same API (datastore2).

Every time it has happened its when when 20+ players join at once, and only effected some players, since some loaded in just fine
When we play with lower count, less than about 12, we are yet to see this error