- Getting started
- Understanding UiPath Robot
- UiPath Assistant
- Installation requirements
- Installing robots for unattended automations
- Configuring robots for unattended automations
- Connecting robots for unattended automations to Orchestrator
- Setting up Windows Server for high-density robots
- Redirecting robots through a proxy server
- Implementing authentication
- Adjusting registry settings for execution in minimized RDP windows
- Using network locations
- Setting up Linux robots
- Configuring package signature verification
- Setting up package folders and network paths
- Configuring activity feeds
- Deploying unattended automations
- Installing robots for attended automations
- Configuring robots for attended automations
- Integrations
- Troubleshooting
Background automations
A background automation can run without interacting with UI elements, and it relies on the background actions to share information. Automations that use UI Automation activities cannot run under a locked screen, therefore they are not suited to run in the background.
Multiple background automations can run concurrently in the same Windows session. Each running automation uses its own set of dependencies. So, if two automations need the same resource but in different versions, each automation uses the specific version it requires.
-
When a Windows system starts up, it creates a Windows session called Session 0. This session runs various system processes that help the machine to operate and it is not associated to any user. It does not have a user interface and cannot interact with sessions initiated by user logins.
-
The login of a user on that machine creates a new session called User Session. This session is used for running user-specific services.
-
Attended automations, when they run in the background, operate within the user session of the user who initiated them. This way, the Robot can retrieve information and access files that are user-specific.
-
Unattended automations are initiated by the Robot Service and run within Session 0. While running in this session, unattended automations are associated with a specific user, and inherit the permissions of that user. Make sure that those permissions include access to the resources the automation requires, since Session 0 cannot access user sessions.
Attended automations are designed to run under human supervision. They are triggered by user events, such as mouse clicks or keyboard inputs, and run on the same machine where the user logs in.
A background execution allows the Robot to run automations in the background, without an active user interface, but for a specific user.
If you have an Attended license, you can concurrently execute only one foreground automation (with UI interaction), and multiple background automations (without UI interaction).
Unattended automations are designed to run natively in the background, without a UI interaction or human supervision. This type of automations usually execute within a Windows session, under the Local Service.
Microsoft applications, such as Excel, Word, or PowerPoint, operate in user sessions. For this reason, unattended automations running in the background might have issues with these apps.
Running several unattended automations at once consumes a separate Unattended license for each one.
You can transition a background automation to a foreground one, by using the Use Foreground activity.
