Control Room license fail-safe and expiry states
- Updated: 2026/05/27
When the Control Room loses connectivity to the Automation Anywhere license server or license consumption exceeds the purchased count, the Control Room enters a fail-safe state. Administrators must resolve the issue within 30 days to avoid a full suspension.
Fail-safe scenarios and license states
A Control Room can enter the fail-safe mode when either of the following conditions persists for more than 48 hours:- The Control Room cannot connect to the license server (connectivity loss).
- The licenses are oversubscribed on the Control Room.
The Control Room is always in one of three license states: Active, Fail-safe, or Fail-safe-expired. Each state determines which license operations are available. The system records each state change in the audit log.
- Active
-
The license server accepts all API calls from the Control Room. Users can be assigned floating licenses when they log in, and licenses are released when users log out.
When the Control Room restarts and establishes connectivity to the license server, it returns to the Active state:
- Users who had licenses assigned before the fail-safe period have their original licenses reallocated.
- New users can request and be allocated licenses.
- Fail-safe
-
Only the heartbeat API call is sent to the license server. All other API calls from the Control Room are stopped.
Fail-safe entry threshold: If the license server does not receive a heartbeat from the Control Room for 48 hours, it considers the Control Room to be in fail-safe mode.
- Fail-safe-expired
-
The Control Room stops all operations and logs out all users.
Fail-safe expiry threshold: If the Control Room remains in fail-safe mode for 30 days without resolution, the status changes to Suspended. Contact Automation Anywhere Support to restore the Control Room.
| Fail-safe entry | Fail-safe expiry | |||
|---|---|---|---|---|
| Due to loss of connectivity | Due to license over-consumption | Due to loss of connectivity | Due to license over-consumption | |
| Days | Two days after loss of connectivity | Two days after over-consumption | 30 days from fail-safe entry | 30 days from fail-safe entry |
| Reason | Loss of connectivity/license server down | License over-consumption. If user licenses are consumed more than allocated, the Control Room displays a message showing the over-consumption | Loss of connectivity/license server down | License over-consumption. (Consumption is more than purchased license count) |
| Remedy | Restore connectivity to Cloud license server | Release over-consumed licenses and sync licenses with the
license server, or renew the over-consumed licenses.
|
Restore connectivity to Cloud license server |
|
| Possible operations |
|
|
|
|
| Notifications | After the initial 48 hours, you will see a banner in your Control Room with a message about the over-consumption | On the 30th day, you will see a 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 | ||