So I have a problem that is occurring at the 'roll over' of Leaderboards.
My leaderboard request is firing off every 30 seconds to get an updated leaderboard. I get the response with the version (Let's say 10). I then request the previous version 9 (version -1), so that I can get last weeks leaderboard, and populate the Reigning Champion (last weeks winner).
At the roll over (Manual Reset, on the hour or when we go live Sunday Midnight UTC), if you're in the area looking at the leaderboard there is a period of maybe up to a minute or more where requests return version 10 still. Looking at the GameManager, the Leaderboard is empty and on version 11.
After a while (1 minute or so) a request will finally return 11.
My assumption is that this period is propagating the leaderboard to various servers and I'm getting 'old' results.
However upon receiving 10 as my version and trying to get 9 I end up falling foul of trying to request an older version, I then get an email from you guys about being over the limit.
Personally I'm not bothered, I don't want a version older than one archive, and I handle the LeaderboardVersionNotAvailable by simply ignoring it. However I do get the emails.
If I keep the current system and go live there's high likely hood that many users are going to be requesting 'over the limit' and I'll be getting spammed with emails.
I'm not sure what your policy is, it says to change the code.. .trouble is I don't know what the current version is at the time I'm requesting it, I'm getting told it's still 10 so I'm requesting 9 during this period.
Can I prevent the emails for this event somehow and just live with the request denied??
Does this bother you guys?
What is the cause of the delay and the return of this version '10' when it should be '11'?
Any suggestions on how else I can handle this?
Cheers