What is the difference between Attended and Unattended Robots?
Feature |
Attended |
Unattended |
Will impersonate a Windows local user to start process execution |
|
x |
Will run on Attended user's computer (virtualized or local laptop or desktop) |
x |
|
Will run on any computer, as long as it's powered on and registered/connected with Orchestrator |
|
x |
The Attended user can set reminders to execute a process (ex: every day at 9am), but human interaction is required to start that process |
x |
|
Strong recommendation to have an Orchestrator connection (for centralized license management, logs and process management) |
x |
|
Process execution can be queued (you can have pending processes on a robot or on a group of robots) |
|
x |
Other processes can start unattended process execution (via the Start Job activity) |
x |
x |
Orchestrator users can initiate the execution of a process from Orchestrator |
|
x |
Must be connected to Orchestrator to function |
|
x |
Gives Attended users access to all other UiPath Assistant features |
x |
|
Centralized Process update mechanism (via Orchestrator) |
x |
x |
Centralized execution logs (info, errors, etc) |
x |
x |
Can be licensed locally |
x |
|
Can be licensed via Orchestrator |
x |
x |
Can execute RPA Processes built with UiPath Studio(s) |
x |
x |
Can execute processes without human supervision |
|
x |
Can execute scheduled Processes (e.g. every day at 9am) via Orchestrator |
|
x |
Can execute processes based on Orchestrator events (ex: queue item added) |
|
x |
Can execute processes based on external events (via Orchestrator API calls - ex: triggered by BPM tools) |
|
x |
Can interact with the Attended user via callouts, forms, input boxes, message boxes, highlighted UI elements or similar |
x |
|
Can run a single process at a time |
|
x |
Can run multiple background processes, usually used to monitor user/application events and then trigger foreground process execution |
x |
|
Can run a single foreground process (a process that interacts with the User Interface) at a time |
x |
x |
Can run processes in "PiP mode" |
x |
|
Can work in tandem with a human, pausing the execution whenever human input is required |
x |
|
Can work asynchronously in tandem with human users assuming the process was built that way (Orchestration Processes) |
|
x |
Attended users can initiate the execution of a process from UiPath Assistant |
x |
|
Attended users can initiate the execution of a process from a browser (via the JavaScript SDK) or from desktop apps (via the Robot API) |
x |
|