Issue
Scheduled RPA Bot fails to unlock machine.
The issue seems to occur after a successful scheduled run of the RPA Bot or after 15mins or more.
Resolution
The machine hosting RPA Central or RPA bot may have a Group Policy that logs out the current user when no activity is detected.
In order for the RPA bot to unlock a machine, it needs to be in a locked/disconnected state. If the session has been logged out, the RPA is unable to log back in.
If the GPO is enabled, it will need to be disabled to prevent this issue from occurring.
This can be done by
- Open the Local Group Policy Editor and browse to:
Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Session Time Limits - In the right panel, double-click the “Set time limit for active but idle Remote Desktop Services sessions” policy.
- Changed this to Disabled
Additional Information