Introducing Datastore Throttle Messages

Updates Announcements
#1

Starting today, we will be sending warning messages to your server console if your datastore requests are being throttle. If this is happening to you, please refer to Documentation - Roblox Creator Hub for information on how many requests of each type are allowed per minute. Also, take a look at the datastore budget tab in the developer console for live feedback on how much budget you have for each type of request.

Example message:
“Request was throttled. Try sending fewer requests. Key = [key]”

43 Likes
#2

Neat! I’ll find this most useful for writing datastores.

1 Like
#3

Cool, this’ll be helpful :smile:

Yep, my datastore requests are being very throttle lately.

2 Likes
#4

Oh yes, oh yes, oh yes, keep it coming with the lovely messages in Public Updates and Announcements.

3 Likes
#5

it seems like limitations changed, I don’t know the last I read it but it seems more lenient now, correct me if I’m wrong

#6

Yup, we’ve been working to improve developer experience with datastores. We’ve managed to loosen up some of those restrictions as we improved our tech.

6 Likes
#7

Would it be possible to raise the limit of HTTP requests that can be made each minute? :stuck_out_tongue_winking_eye:

3 Likes
#8

This will be so helpful! Keep up the work with the recent updates.

#9

Very helpful change. Thank you.

#10

thanx

#11

What does it mean that it was “throttled”? Did my request still go through successfully? Was it just delayed a bit?

#12

I don’t see in which case you would ever need more than 500 requests a minute.

What exactly are you trying to do?

1 Like
#13

If a request is throttled, it is usually only delayed. This is ok if you are throttled only a few times. However, if you are recieving a large number of throttles, it becomes increasingly likely your request wont go through at all due to a backlog of throttled requests. If you see yourself in this situation, you may want to look into how you are using data store and look for ways to reduce the number of requests.

1 Like
#14

Awesome, thanks! I believe my issue was due to me setting a key every 5 seconds, and it looks like the doc says that there’s a 6-sec cooldown.

#15

Nice! Good to see the wiki helped you find the issue :smiley:

#16

I have a system I made for achievements and other things in game and all the data is stored on my website. I don’t want to take up all 500 requests so game creators can’t use HTTP, so I try to limit what all I use.

PS. That’s one of the 3 things that got me into RDC then into the DevForum.

2 Likes
#17

Wish datastore limits could be raised tho…

#18

If the current limits are too low for you, you should post a feature request explaining what you’d like to but are unable to do with the current limitations. It’s more than likely not handling DataStore requests appropriately though, so I would first post a help thread in #development-discussion asking if there’s any way you can optimize the usage of your DataStore requests.

#19

its not that its a problem for me. its just it would be nice.

#20

Why would it be nice if there’s not a problem to begin with?