Best way to spread out data store saving?

So, I have a global leader board and want to stop data store limits from stopping it from refreshing.

  1. The issue is though, that because of data store limits it sometimes won’t refresh, with this error:
20:13:00.913 - DataStore request was added to queue. If request queue fills, further requests will be dropped. Try sending fewer requests.Key = 703332131 
  1. At first I tried making each of the four different global leader boards refresh on different multiples of 30, but i found out that it would sync up again and cause the error, then i tried:
    50, 105, 130, 175
    That worked for a bit until it synced up again, but it doesn’t do it frequently.

But, I’m still not that satisfied with the errors in the first place, and I would like to know if there is a number sequence with for 4 different global leader boards that won’t cause errors or sync up again.

Thank you for reading, and if I missed anything please tell me.

If you wait 15-30 seconds before starting each leaderboard’s saving loop, the saves will never sync. Before starting the save loop, just wait a small amount of time that is different for each leaderboard.

For instance, just do something like this when your server is first started up:

spawn(startleaderboard1)
wait(15)
spawn(startleaderboard2)
wait(15)
--ect.

Instead of making the refresh wait() time different for every leaderboard, just change the time before the initial save.

Good luck with your leaderboards!