We are looking to identify the cause of an "App is disabled." error.

We recently noticed this error logged temporarily in our live service. We want to clarify that we did not explicitly change the app's enable/disable settings at any point.

However, we found that the exact timing of these error logs coincided with when we were deploying to the target app via the Builder API.

We would like to know: is this temporary "disabled" state a known or expected behavior while a deployment is in progress via the Builder API?

Thank you!

Added the additional details to 13660

Q1: The removed player is completely excluded from reward calculation, so if the deletion happens before the job runs, that player is never iterated over and receives no rank or rewards.
Q2: Yes, the modified score will be used. The job always reads live state. Note that whether the score actually gets modified depends on the leaderboard type (e.g., for the LOW_VALUE type, only updates if the new score is less than the existing)
Q3: No backfilling, the next joiner goes to the latest instance, not the freed spot in ^2. No loop over earlier instances (^1, ^2) ever happens. The next joiner goes to ^3 (or ^4 if ^3 is full). The freed spot in ^2 stays empty permanently.

brainCloud developers have just release several playable builds of our famous examples! See our cool features in action. Find them at https://getbraincloud.com/demos for Windows, Mac, online and mobile.