Overview
Unattended executions, such as scheduled tasks, API-triggered executions, or remote scheduling, require an active Windows desktop on the robot's host machine. An active desktop is necessary for any automation process that interacts with UI elements like client applications, images, or mouse and keyboard inputs.
This product provides a desktop rendering maintenance feature. However, due to the complexity of the Windows operating system, the variety of virtualization solutions, and host security restrictions, it may not be effective in all situations.
The following solutions are recommended based on the type of Windows host for your robot:
Host type | Recommended solution |
Wuying Workspace | Note Whenever possible, use Wuying Workspace as the robot's host. Wuying Workspace ensures continuous desktop rendering by default. |
Virtual machine | Use the local method for desktop rendering maintenance. Note If the virtual machine is an ECS instance, this method is recommended. Important Prerequisites for using the local method for desktop rendering maintenance:
|
Physical machine | Keep the monitor on at all times and disable any Windows settings that could interrupt a persistent desktop session, such as screen savers, automatic screen-off timers, and sleep mode. |
Configure desktop rendering maintenance
After an on-premises robot connects to the RPA server, you can configure desktop rendering maintenance from the On-premises Robots > Robot Monitoring menu.
Local method
The local method uses the native Windows console session to maintain desktop rendering. You can enable it in two ways:
Method 1: Configure this setting in the console. Before an unattended task (such as a scheduled task) begins, the robot client automatically switches the current Windows session to a console session based on the configuration.
Method 2: Manually switch using the on-premises robot client. Right-click the application icon in the system tray and select Start local desktop rendering maintenance. If you are accessing the Windows host via Remote Desktop, this action will disconnect your RDP connection.
You can view the status of an on-premises robot client running in a Windows console session from the On-premises Robots > Robot Monitoring menu.
Use desktop rendering maintenance
Scheduled trigger
In the On-premises Robots > Scheduled Task Management > Scheduled Tasks menu, create a scheduled task and enable Desktop Rendering Maintenance for the selected robot.
Before dispatching a task to an on-premises robot, the server enables desktop rendering maintenance according to the configuration.
API trigger
When calling the createServiceTask API, set renderEnabled=true to enable desktop rendering maintenance.
Runtime behavior
Local method
Before the task executes, the server instructs the client to switch the current session to a console session.
During task execution, we recommend that you do not remotely access the host machine (for example, by using an RDP client).
Doing so will cause the desktop resolution and DPI scaling to switch to the RDP client's settings, which may disrupt the automation process.
If you close the RDP client connection before the task is complete, the automation process may fail due to an interruption in desktop rendering.