I am most certain that it is not the process or the selector issue. This most probably is the authentication issue. Let me explain.
- Ensure you have the right robot user logging into the robot machine with the correct domain\username and password (windows credentials or pin etc.).
- Robot machine is connected to Orchestrator and UiPath.Service.UserHost service is running in the background
How to check if this is the case?
- Use a global handler in your process and use the exception message generated to take a screenshot
- If when you login (as robot user) after the robot failed and you see applications being opened from the previous login. It mostly is the robot which opened them during execution but never got to close them due to the inability to access the selectors.
When using a robot in unattended mode and when you get such an error, the first thing you need to check is if the robot was able to log into as a user of the machine.
Both UiPath and BluePrism robots have the ability to launch application from the login screen especially if it is a browser based automation. The robots can launch applications but if they want to use anything other than simulate actions (simulate click or type into) the window they see is a login screen and will not have access to the UiElements/Selectors of the application.
For example: A process which is
- Opening browser – Robot launches this from Login Screen
- Clicking Home button simulate action --Robot can perform this a well
- Typing into a text field – Robot fails as it does not have access to identify a selector