To Run Background Automation, you need to understand the process and its component. Check out this post to find out more.
Automation of Background Processes
An Attended Robot works on the same machine as a person does. It triggers by user events and should only execute with human supervision. Learn more about the Robot’s license-based automation possibilities.
Background A Robot performs Process Execution on a computer for a specific user. Processes run concurrently in the same Windows session.
Even if several operating processes require a different version of the same requirement, each running process utilizes its own version of dependencies. For example, if process A requires dependency v18.4.6 and process B requires dependency v19.4.4, then each process downloads and utilizes its own dependent version.
This sort of license allows an Attended Robot to run one foreground process (with UI interaction) and several background processes at the same time (without UI interaction).
When your automation project requires interaction with UI components, a foreground process does employ. These procedures make extensive use of UIAutomation activities. Please keep in mind that you may only run one foreground process at a time.
Background processes do not need to interact with UI components on the screen and instead rely on background processes to pass the information along. In these project categories, UIAutomation activities should not utilize. Multiple such processes can operate on a computer at the same time, even if a foreground process is already running.
The behavior of Attended and Unattended Robots
During startup, a Windows Session does establish for System Processes that are not associated with a specific user to execute; this is known as Session 0. This session enables Windows to perform system processes required by the computer.
For a more thorough explanation, see Microsoft’s Session 0 Isolation paper. Also, it explains how sessions do establish and information is handled between them.
When running under Attended vs. Unattended automation, background processes behave differently. Background processes initiated by an Attended Robot execute in the user’s session, whereas those initiated by Unattended Robots execute in the Windows Session.
Robots that were present
Background Process Automation with Attended Robots runs automation in the same Windows Session as the user. These do launch from Studio or UiPath Assistant and run in the same Windows Session as the user. Because the automation occurs inside the same session, the Robot may get information and access files that are unique to the user.
Robots Left Alone
Background Process Automation with Unattended Robots does initiate using the Robot Service and executed in the Windows Session. It is critical to understand that Session 0 lacks a User Interface and cannot communicate with a user session. When running this kind of process on Unattended Robots, bear in mind that they run in the user’s name and inherit the user’s rights.
Ascertain that the user who runs the process has access to the necessary resources and that the process does not necessitate the usage of a User Interface. More information on how the UiPath Robots manage windows sessions may be found on the Windows Session page.
How To Run Background Automation?: Background Processes Are Running
With the v2020.4 Release, you may use Use Foreground Activity to move a Background Process to the Foreground. More information on how this activity works and how to include it in your routine can be found here.
In Orchestrator, the Robot is tagged as Busy as long as at least one process is ongoing.
It is not feasible to start another foreground process when another is currently executing. Background processes, on the other hand, can begin independently of the status or nature of other processes.
In your background processes, you may utilize the Run Parallel Process action to launch other processes based on the triggers you require. This activity’s processes execute separately.
A background process that monitors certain activities, for example, can launch a new process (Foreground or background) and continue to monitor the specified activity without being stopped. Even if foreground and one or more background processes are already running, a background process loaded by this action begins immediately. Also, if the action initiates a foreground process, one of the following events occurs:
- If there is no other foreground process running, the process begins immediately.
- If a foreground process is already executing, an exception is fired.