"508: Exhausted all retries for key: %s string" datastore error happens when I haven't gone over my limits

Oh, I never knew about that. Thanks for the tip!

1 Like

I started getting this error as well 3 days ago. I can not find any solution to fix it so I just gave up.
it only happens in some games because I tested my old games and datastore worked fine.
roblox has not said anything about 508 error anywhere.

it still happens to me.image

even if i used

game:BindToClose(function()

end)

?

This is true regardless of how you are testing, there’s nothing you can do in playtest in-game vs studio.

I answered another thread with the same question before I noticed this one; 508: Exhausted all retries for key: %s DataStore

based on this bit of code; this example could also be afflicted by the same answer I gave there

local key = os.time()
key = tostring(key)

i am not fully sure if that is the problem because i started getting this error 3 days ago iv always coded this way and never got an error from it.

	local Data;
	local Error,Done = pcall(function()
		Data = GetDataStore:GetAsync(Plr.UserId);
	end)
	if (Data) then
		Stat.Value = Data[1];
	end
1 Like

Just saying but your code can be cleaned up a lot more easier by this bit of code:

local Success,Data= pcall(GetDataStore.GetAsync, GetDataStore, Plr.UserId)

if (Success and Data) then
    Stat.Value = Data[1];
end
1 Like

Thanks for advice i will use it in future :heart: .

Ive noticed this happening as well but it seems to only affect a small group of people in my games:

Ironically this just started happening for me as well, despite using alphabetic keys. It’s totally hit or miss but appears to happen more frequently in studio than in game.

1 Like

this kills my game

I’m getting this error too, absolutely no clue what is going on. Are you sure it’s fixed?

2 Likes

If this is still a problem, please file a Bug Report. Using this thread is not the appropriate answer to continue inspecting an issue that developers have no control over.

It seems to be a problem on Roblox’s end.

1 Like

When did you first receive this error? Does this apply to ordered data stores, standard data stores, or both?

Yesterday on Standard Data Stores. It’s intermittent, though, and changing key fixed it (for now). I can’t say whether it’s happening on Ordered Data Stores however, sorry.

4 Likes

This may or may not be helpful, but I am getting this error as well. I have two games using the exact same DataStore code and one gets this error when closing Play Solo in Studio and the other does not.

1 Like

I can confirm it’s happening for Ordered Data Stores.
Also this happened to me 6 days ago

2 Likes

Couple days ago, occurs on data stores, seems to be tied to the key itself, changing the key seems to work. Can read fine, issue is with saving.