brainCloud personnel
Posting a copy of the AWS service health page for posterity.
It mostly refers to the outage impacting DynamoDB - but a lot more services than that were impacted. We expect that just means that a lot of AWS services use DynamoDB under-the-covers to operate.
Our alerts have all clears (gone green) - and we now have access to StatusPage and Intercom again. It looks like things are back to normal <knock-on-wood>.
Be sure to double-check your apps - especially any recurring scheduled cloud code job - to ensure that they are still scheduled to run at the normal schedule... [delayed job processing appears to be one of the impacts of the outage - likely due to delayed AWS SQS (queue) processing].
If your app is still seeing issue - be sure to let us know via the Intercom support (which is working again)!
It looks like things are getting back to normal. Error levels are coming down - and we're seeing new hosted server launches again.
Hi folks,
An AWS outage in the us-east-1 region (which is the central brainCloud region) is currenty affecting brainCloud. More info here - https://health.aws.amazon.com/health/status
It most specifically seems to be affecting the ability of customers to download files - and launch new hosted servers.
It is also affecting our ability to log into Intercom, the chat service we use for support, and StatusPage - the service that we use to describe brainCloud health! (https://braincloud.statuspage.io/) (or else I would be posting this there!).
Anyway - AWS folks are on the issue - and hopefully things will be resolved soon!
Paul.
In both cases, the transactions should already be recorded. In your iTunes case, you might have purchased in a sandbox environment. You just need to enable Sandbox Transactions, and those transactions should then appear there.
Hi,
Actually - voting leaderboards are implemented via the PostScoreToLeaderboardOnBehalfOf() call - where you can basically vote for someone else's score. [i.e. voting for that person].
Create the leaderboard as a "Cumulative" leaderboard - and basically the player votes for the score of another player - incrementing it by +1.
I suppose we should add those details to the roadmap item!
I hope that helps to clarify things!
Paul.
Thanks for pointing that out. This type of leaderboard isn’t directly supported by the current leaderboard APIs yet, but I’ll forward your feedback to our team for review.
In the meantime, as a workaround, you can create a Cloud Code script to handle it like a voting system -- the script can retrieve the player’s score and then post an additional “voted” score on behalf of that player.
As I mentioned in the support chat - the issue is that midnightPSTinUTC isn't dynamically calculated for midnight today -- it's midnight PST on Oct 4th. [i.e. over a week ago].
What's happening is the call is accepting that past date - which puts the script in the front of our queue to be run ('cause we think we're late!) - and it gets run in the next 60 second job interval. And then reschedules itself in the past again.
So basically this script is running roughly 60*24 = 1440 times a day.
Anyway - I'll have the devs look into it - we should return an error if you are scheduling the script too far into the past... [i.e. a second or two in the past is probably fine - and best to do in case the scheduling script has delays of some sort... but clearly 10 days in the past is too far! Probably 60 mins in the past is too far! 
]
@larrybiely over 12K API calls a day? Hmm - I'll take a look at that script...
The API calls should come from your script, not from the scheduled task itself, right? Here’s an example of how to set up a daily execution script for your reference -- https://github.com/getbraincloud/examples-unity/tree/master/Invaders#schedule-a-cloud-code-script-to-protect-replays-from-deletion-for-top-10-and-featured-players
