Control Room fail-safe status

The Control Room connects to the Automation Anywhere Cloud license server and obtains license entitlements based on the license key that is installed on the Control Room.

A Control Room can enter the fail-safe mode in one of the following scenarios:
  1. When the Control Room cannot connect to the license server, it moves into the fail-safe status.
  2. When the licenses are oversubscribed on the Control Room, the Control Room moves into the fail-safe status.

With respect to the Control Room license server database, the Control Room is in one of three states. These states indicate what user licensing actions can be performed. With each state change, an entry is made in the audit log.

Active
Normal operations. All API calls from the Control Room are accepted by the license server.
Users can be assigned floating licenses as they log on. Floating licenses can be released as users log off.

When the Control Room is restarted and operational, and connectivity to the license server is established, the Control Room is in the Active state:

  • Users who had licenses assigned prior to the fail-safe have their original licenses reallocated.
  • New users can request for and be allocated licenses.
Fail-safe
Only the heartbeat API call is allowed to the license server. All other calls from the Control Room are stopped.
  • Fail-safe entry threshold: If the license does not receive the heartbeat from the Control Room for 48 hours, then the license server considers that the Control Room is running in the fail-safe mode. This 48-hour period is called the fail-safe entry threshold.
Fail-safe-expired
The Control Room stops all operations, and all users are logged out of the Control Room.
  • Fail-safe expiry threshold: After the license server moves a Control Room into fail-safe mode, it waits up to 30 days to reinstate the license. After 30 days, the status is changed to Suspended, and you need to connect to technical support to restore the Control Room to fail-safe mode.
Fail-safe entry Fail-safe expiry
Due to loss of connectivity Due to license overconsumption Due to loss of connectivity Due to license overconsumption
Days Two days after loss of connectivity Two days after overconsumption 30 days from fail-safe entry 30 days from fail-safe entry
Reason Loss of connectivity/license server down License overconsumption. If user licenses are consumed more than allocated, the Control Room displays a message showing the overconsumption. Loss of connectivity/license server down License overconsumption. (Consumption is more than purchased license count.)
Remedy Restore connection Release overconsumed license and sync license with LS or renew the licenses overconsumed.
  • You can remove the extra licenses associated with users and resync with the license server by clicking Sync license from server.
 Restore connection
  1. Renew the overconsumed license.
  2. Raise support ticket to restore fail-safe entry, and then release the overconsumed license and sync data with license server.
Possible operations
  1. Only license allocation and deallocation is allowed. The data is later synced when connectivity is restored.
  2. Both admin and non-admin users are able to log in.
  3. Banner is shown when you log in, along with error message on the license page.
  4. RPA operations continue normally.
  1. All license operations are allowed
  2. Both admin and non-admin users are able to log in
  3. Banner is shown when you log in along with error on license page, along with license overconsumption error on license page.
  4. RPA operations continue normally.
  1. Only admin user can log in. Non-admin users cannot log in.
  2. No license operations are allowed
  3. Banner is shown when you log in along with error message on license page.
  4. RPA operations cannot continue.
  1. Admin can log in and install licenses.
  2. No license operations are allowed
  3. Banner is shown last day before the Control Room shuts down along with overconsumption error on license page
  4. RPA operations cannot continue.
Notifications After the initial 48 hours, you will see a banner in your Control Room with a message about the overconsumption. On the 30th day, you will see the banner with a red background and a post that the user will not be able to log in. After the 30th day, you will not be able to use the Control Room.