Configure auto-login settings in the Control Room to either create user sessions or reuse existing user sessions to reduce the automation startup time.

Prerequisites

Ensure that you are logged in to the Control Room as the administrator.

Note: If the Bot Runner device disconnects every time a session logs off, ensure that you log into the device with an administrative account and run this command in the Terminal application: sudo pmset -a powernap 1 tcpkeepalive 1
Auto-login enables you to deploy an automation for unattended Bot Runners after automatically logging on to a machine and restoring the machine to its original locked/unlocked state after completing the deployment.
Note: The Run as user device credentials are used for Auto-login.

Configure auto-login settings to either create new user sessions or reuse existing sessions in the following scenarios:

  • Before deploying an automation, some applications are kept running to accommodate a delay in the application launch.
  • Logging off from temporary or non-persistent devices stops automation execution.
  • You can reuse existing user sessions when your company's IT policy prevents you from providing device user password for auto-login credentials.

Procedure

  1. Navigate to Administration > Settings > Devices.
  2. In the Auto login settings, click Edit.
  3. Select one of the following options on how you want the sessions to be created for running automations:
    • Always create a new session

      Select this option for desktop deployments where it is possible to create user sessions on devices.

    • Reuse an existing session

      Use this option for deployments on devices where it is not possible to create user sessions.

      Select this option for auto-login settings in the Control Room to use event triggers on unattended Bot Runners and to run automations when a device is locked or is in a disconnected state.
      Note: When you use the Reuse an existing session option, ensure user sessions are available. If there is no existing user session, triggers and automation deployments will fail.
    • Reuse an existing session, if available
      Use this option if you must create a new session. If a session does not exist, create a new session and leave it unlocked for next user session after automations complete their run from the following:
      • A new session
      • An existing locked session
      • An existing unlocked session
      • A disconnected session
  4. Select one of the following options for the new session when the automation completes:
    • Log off
    • Leave the session unlocked
    • Lock the session
    Similarly, you can select the options for an existing locked session, an existing unlocked session, and a disconnected session
  5. Optional: Select one of the following options if you want to allow or restrict users from changing these settings individually for each device:
    • Allow changes
    • Do not allow changes

      Is the default setting and disables the user-level auto-login settings for user sessions.

  6. Click Save changes.