All Collections
Portal Pages
Design | Core App Info | Advanced Settings
Design | Core App Info | Advanced Settings
Paul Winterhalder avatar
Written by Paul Winterhalder
Updated over a week ago

You can control various miscellaneous settings for your brainCloud app on the Advance Settings page.

These settings control key aspects of brainCloud behavior. Be careful with them!

Choosing Core App Settings


  • Disabling your app will prevent your end-users from accessing your app. You can still access your app from the dashboard, to make API call and configuration edits. 

  • Use this option if you have outstanding reasons to disable your app, such as taking your app down for temporary maintenance. 

  • The disabled reason will be returned as JSON when your customers try to access your app.

  "status_message": "Processing exception (bundle): App is disabled.",
  "reason_code": 40330,
  "severity": "ERROR",
  "disabledReason": {
    "message": "MyApp is disabled for maintenance from 6:00-8:00 UTC. Please return later."
  "status": 403

Generate User Statistic Rule Enabled and Generate App Statistic Rule Enabled

  • These two toggles will allow if new statistics can be created via API calls. If you wish for statistics to only be manually created via the dashboard in the Design | Statistic Rules section, keep these toggles disabled

Will you only create stats on the brainCloud portal? If so, keep this toggle off to prevent the client app from unintentionally making new stats!

Disable Live Lock (not recommended)

  • The Live Lock will prevent your development team from making accidental changes in the app. They can click on the Live Lock banner to temporary disable the lock unless they do not the permission levels required.

  • Disable this option with caution!

Real-time Tech (RTT) Enabled

Your App’s Compatibility Settings

Features have been added and modified throughout brainCloud's development, and as we continue to grow to the service.

Our development team prides itself on not breaking reliant apps by one of these changes. We recommend and encourage developers to keep up to date on our latest libraries. However, we will create a compatibility flag for any breaking change, and automatically grandfather in existing apps to keep using the old features. Your development team can update at their own pace.

To understand what each compatibility flag does, find more on our Compatibility Settings page.

First time creating an app on brainCloud? Then none of these Compatibility Settings will be relevant to your current app but know your existing app will be secure in future changes 😊

Session Behavior

  • Use Session Timeout to control how long it takes for your users to timeout of brainCloud. Your app will keep the brainCloud session alive as long as the end-user has your app opened. If that customer were to exit your app, the session timeout limit would then apply. For example, they would have 20 minutes to return to your app before they would have to reauthenticate their session. If applicable, you can decrease the session timeout limit.

  "status_message": "Session expiry exception (bundle): user session has expired: 9htmpnjs1fo7ujfdhq4bu5o2t6",
  "reason_code": 40303,
  "severity": "WARNING",
  "status": 403
  • The Maximum Concurrent Sessions per Player controls how many sessions a user can create at the same time. Newer user sessions will invalidate older ones. If you are making a game, you will probably want to limit one session per user to prevent cheating. However, if you are making an app, you may not see a reason to impose a one session limit.

  "status_message": "Processing exception (bundle): User session logged out by other login",
  "reason_code": 40356,
  "severity": "ERROR",
  "status": 403

Did this answer your question?