- Getting started
- Best practices
- Tenant
- Folders Context
- Automations
- Processes
- Jobs
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Identity Server
- Authentication
- Integrations
- Classic Robots
- Troubleshooting
Managing Robots
In modern folders, there is no robot management per se, as robots are created automatically. However, you are required to define the licensing, execution, and authentication aspects of the robot to be created. Find below the steps to have a functional setup that allows you to execute jobs in modern folders.
In attended mode, the UiPath Assistant shows the processes across all the folders the account is assigned to.
These processes cannot be started or triggered in unattended mode from Orchestrator unless it's for debugging purposes. See Studio design and Orchestrator debugging.
In unattended mode, the UiPath Assistant shows the processes across all folders to which both the account and machine template have been assigned. These processes can be started or triggered in unattended mode from Orchestrator.
A user using an unattended robot in attended mode (the user logs on to the machine) does not have access to the processes in folders to which the user alone is assigned. Their access is restricted to processes found in folders to which both themselves and the machine template are assigned.
Dynamic Allocation Usage Convention: On a host machine you need to provision a Windows user for each account that belongs to the folders to which the corresponding machine template is assigned to.
Say you connected a server to Orchestrator using the key generated by machine template, FinanceT. That machine template is assigned to folders FinanceExecution and FinanceHR, where 6 accounts are assigned as well. Those 6 accounts need to be provisioned as Windows users on the server.
Graphical Representation of a Basic Modern Unattended Setup
Graphical Representation of a Complex Modern Unattended Setup
When interactive authentication is enforced, in UiPath Assistant you can only see the processes to which you have access and only after signing in to your account. A user license is also required. Therefore, unattended processes which do not run under your account are not available in UiPath Assistant for troubleshooting.
So, if you need to debug an unattended process, you can temporarily enable a troubleshooting session. Doing this lets you 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.
When you have finished debugging, you can disable the troubleshooting session for the machine so that it won't allow attended connections anymore. Or, if you need to, you can extend the amount of time that the session is active.