What steps need to be done in order to see processes in UiPath Assistant for Unattended Robot user(s)?
Issue Description
In the UiPath Assistant the processes are not displayed for the Unattended Robot user.
Below is the only shown message in the Processes widget of UiPath Assistant
"Connected as Unattended Robot Unattended automations will run as expected. To see the automations here, enable the troubleshooting session from the Orchestrator"
Root Cause
This is an expected behavior for Unattended Robots to not be able to see the processes in the UiPath Assistant processes widget when the Interactive Sign is enforced in Orchestrator UI -> Tenant -> Settings -> Robot Security.
The processes widget in UiPath Assistant is designed in general for the UiPath Attended Robots which relies on running the attended jobs through it.
Resolution
Prerequisites
-
Connect the Robot to the Orchestrator using a machine template. Using Client ID credentials for connection is advised.
-
Add the Unattended Robot and machine template to the Modern Folder(s) containing the processes that need to run.
-
Verify that the Unattended Robot is assigned with 'Allow to be Automation User' role at the tenant level and 'Automation User' role at the folder level.
-
Utilize the latest Enterprise Robot version patch for the newest improvements and bug fixes. Check the Release Notes for the Robot product.
To see the processes for Unattended Robots, there are multiple approaches to choose from.
Approach #1
Works for Robot User Accounts:
- Navigate Orchestrator UI -> Tenant -> Settings -> Robot Security.
- Enable 'Hybrid for Attended and Unattended Robot authentication'.
- Click 'Save'. Now, the Unattended Robot processes should be visible in Assistant which are only using the Connect option.
Approach #2
Works for Robot user accounts:
- Go to Orchestrator UI -> Tenant -> Settings -> Robot Security.
- Enable 'Hybrid' for Unattended Robot authentication and 'Interactive Sign-in SSO' for Attended authentication.
- Click Save.
- Then, navigate to Orchestrator UI -> Tenant -> Monitoring -> Unattended session
- Locate the correct connected session, click 'Configure troubleshooting session', provide the desired timeout (maximum is 2160 minutes), then click 'Save'.
Approach #3
Does not work for Robot user accounts; if it is possible to Sign In to Orchestrator UI and view the processes in UiPath Assistant, it means a different Attended Robot user is being used.
- For a local user or Directory User Robot functioning as an Unattended Robot, allow an Orchestrator UI profile in Tenant -> Manage Access -> Edit Robot -> General details.
- Connect the Unattended Robot to Orchestrator UI using Client ID connection details and finally Sign In using the Unattended Robot account user.
After performing any of the above approaches, the UiPath Assistant should now display the processes for the Unattended Robot user account.
Example:
Approach #4
Governance Policy on Attended Robot: A governance policy might be restricting the Attended Robot from displaying processes.
Cause: Check the UiPath Assistant under Preferences > General to see if any governance policy is linked.
Governance policies may be linked in two locations:
- Automation Ops: Verify if the policy "Allow users to run automations outside Personal Workspace" is enabled.
- agent-settings.json: Located at %userprofile%\AppData\Roaming\UiPath, where default policies are applied.
If using agent-settings.json, modify it by adding the defaultNugetWidgetConfig property under the agent tag.
Reference: Assistant Governance - Feature Toggles Tab
Solution: After identifying and adjusting the policy, open Assistant settings from the Taskbar, right-click, and select "Refresh policy" to resolve the issue.