We have configured unattended robot ( community edition) on Vmware VM (Windows server 2016 standard OS)
Memory : 16 GB
Screensaver is NOT disabled
We have configured queue trigger to start the process
First transaction is triggering properly and it is working fine (when RDP of unattened robot machine is maximized in my machine)
Second pending transaction will take 15-20 minutes to trigger
If the RDP is minimized or maximized in my machine … The second process is triggered by queue trigger…
But only first activity is running (ex : Login popup to login into portal) and it is stuck in the same place and then getting below error
Status : Reason: The process got faulted unfortunately at : UiPath.UiAutomation.Activities due to : Timeout reached.
Please let me know the best practices to run pending transactions ( queue trigger) without any issues
It looks like something because of UI based activities
Pls run in debug from studio and see at which activity it is getting failed
And I believe it would have happened because of RDP being minimised
And that can be managed with remote connection settings
Do we have signout all the user from unattended robot machine? if we signout all the user, then how the process will run on unattended machine( like opening website and click activity…etc)?
All the setting mentioned in screenshot is already applied
Thank you… I have changed the registry settings… Let me add two transactions in queue (Queue trigger) and Let me check if the second transactions is running without any timeout issue… I will update the status to you… Thank you
Ideally if you are using an Unattended Robot, then you have the UiPath Robot installed and registered as a service on the host machine, so it is listening for new instructions.
If you are using credentials of a user than by default it will connect to the same session that is already in use when Login To Console is set to False, if you wanted it to connect to a new session, you’d have to change your local machine policies to allow it.
