Auto Logon

Auto Logon enables a machine to automatically sign in to a specified Windows user account. Instead of requiring manual login after every system startup, restart, or when the machine returns to a locked state, the system automatically restores the configured user session. This ensures the machine is ready for automation without requiring manual intervention.

This feature is particularly useful in automation environments where workflows interact with desktop applications or UI-based automations that require an active Windows session. If the machine is at the login screen, such automations cannot proceed until a user signs in.

Auto Logon manages the Windows user session and helps ensure that the machine remains available for automation workflows.

Auto Logon provides the following capabilities:
      • Automatically signs in to the configured Windows user account.
    • Restores the user session after machine restarts or when the session is locked.
   • Enables UI-based automation that requires an active desktop environment.
     • Helps maintain a consistent session environment for automation workflows.

Auto Logon is commonly used in the following scenarios:

• Remote Access Environments (RDP)
When machines are accessed through Remote Desktop, sessions may become locked or return to the login screen. Auto Logon ensures the machine signs in automatically so that automation workflows can continue to run.

• Dedicated Automation Machines or Virtual Machines
Automation machines and virtual machines may restart as part of infrastructure maintenance or system updates. Auto Logon ensures that the system automatically restores the user session after startup, making the machine ready for automation.

• Image-Based Automation Workflows
Workflows that rely on image recognition or screen-based interactions require a stable desktop session. Auto Logon helps establish the session using the configured display settings, which helps maintain consistency during automation execution.

It is important to note that Auto Logon manages the Windows user session, not the machine’s connection to the Manager. A machine may remain connected to the Manager, but UI-based automations still require an active user session for execution.

Prerequisites

Before using Auto Logon, ensure the following conditions are met:

• Auto Logon Configuration
Workflow execution begins only after the Auto Logon feature successfully restores the user session.

• Remote Desktop Protocol (RDP)
Remote Desktop Protocol (RDP) must be enabled on the machine to support remote automation scenarios. This allows the Runner to establish a remote session and execute workflows.

• User Account Permissions
The user account configured for the machine must have permission to log in through RDP. The user should belong to the Remote Desktop Users group or have equivalent access rights.

• Single Active Session per User
Multiple users can be configured for Auto Logon on the same machine. However, only one active session per user is allowed at a time. If multiple sessions exist for the same user, Auto Logon or Auto Unlock may not function as expected.

Resolution Behavior in VDI Environments

Auto Logon creates a Windows user session and applies the resolution and scaling settings configured for the workflow. This helps provide a consistent display environment for automation, particularly for workflows that rely on image-based activities.

However, depending on the VDI platform configuration, the desktop resolution may still change after the session is created. In many cases, the VDI infrastructure manages the display settings and may override the resolution applied during Auto Logon.

This may occur in situations such as:

• Dynamic resolution allocation
Some VDI platforms adjust the desktop resolution based on the client device used to access the virtual desktop.

• No active client session
When no client device is connected, the VDI environment may fall back to a default resolution.

• Session recreation
In some cases, the VDI platform creates a new session instead of unlocking the existing one, which can reset the display settings.

• Display protocol policies
Certain remote display protocols may enforce their own resolution settings.

Since image-based automation relies on a stable screen layout, any change in resolution or display scaling may affect execution.

Recommendation: For environments that depend on image-based automation, configure a fixed resolution and consistent display scaling within the VDI platform to maintain a stable execution environment.

Limitations
Manual unlocking of the machine through RDP may not apply the resolution settings configured for the workflow.

Machine Remains Locked for an Extended Period

If the machine remains unused for a long period, the system may enter a locked state (Windows lock screen). When this occurs, UI-based automation workflows may not run automatically.

In such situations, the connection between the Manager and Runner may also be interrupted, which stops the bot from executing workflows. When the Runner becomes unavailable, the Manager may display a warning message such as: “The machine was not last seen for 15 minutes.”

To restore automation, the machine may need to be manually unlocked.

Steps to Restore the Session

1. Log in to the machine manually using the required credentials.
2. Ensure the machine is active and properly connected to the Manager.
3. Once the Runner reconnects automatically (usually within 60 seconds), you can initiate the bot to run again if required.