Assistant - Timeout error on AWS

[wasea (Vasile)]

Hello @Edgar_Bravo ,

Attended processes don’t work under locked screen.
So, when you close the application, the assistant will stop or return an error.

under locked screen, only the unattended processes work (where you need the orchestrator.)

More info here:

Automation Works in Attended Mode but Not in Unattended Mode

How to resolve when the automation works in Robot's Attended Mode but when Not Unattended Mode ? Issue Overview : When an automation is run in Attended mode (i.e. with a human user is logged in and watch the Robot) it works. But when it is run in Unattended mode, it fails. Other symptoms can be that the Robot is clicking in the wrong location, that a random window was opened, items from the task bar are opened or that the application is in an unexpected state. Scenario Description: Automation …

(At the same time, I heard scenarios, keeping sessions up with Anydesk or other third party tools )

I hope it helps.

Vasile.