When interactive authentication is enforced, in UiPath Assistant, a user can only see the processes to which they have access and only after signing in to their account. A user license is also required. Therefore, unattended processes which do not run under a user account are not available in UiPath Assistant for troubleshooting, making it impossible for a user to debug an unattended process by logging into that host machine.
To overcome this, an administrator can temporarily enable a troubleshooting session on their machine. Doing this lets the user see and run the unattended process locally, without requiring a user license. The troubleshooting session is temporary and the above only applies while troubleshooting is active.
You can also use Studio for its remote debugging capabilities. It allows running and debugging attended and unattended processes on remote machines, including on Linux robots that can run cross-platform projects.
Step 1. Enable a troubleshooting session
- Go to Tenant > Monitoring.
- Select Unattended sessions from the Section dropdown menu.
- Identify the machine where the error occurred, click More Actions at the end of the machine row and select Configure troubleshooting session.
The option is only available if interactive authentication is enforced.
You can find out on which machine a process ran by selecting the Processes section.
The Configure troubleshooting session dialog opens:
Figure 5. Configuring troubleshooting session
- Under Troubleshooting session, click the toggle to switch it to Enabled.
- In the Session timeout (minutes) box, edit the value to change the number of minutes the troubleshooting session should be active.
