How to always force a Background Automation to run even when other automations are running at the same time?

Help Orchestrator
,
1

Hello, I have a problem with a very time sensitive automation. Its a background process within the properties of the automation. There is no UI activity. The problem is sometimes I have another processes running on a server, but I need the background process to run at the same time because it is time sensitive.

My understanding is that background processes CAN run at the same time as others, as long as its a background process, but the problem is that it will still wait/pending until the job before it is complete before running.

Question: how do I make sure a background process ALWAYS runs? Does it need to run as NT AUTHORITY\LOCAL SERVICE for it to always execute, and if so, how to i always force it to use that host identity?

image
image346Ă—106 4.89 KB

2

Hi @BrianaB,

If another process is running at the same time bot will wait to complete the process
BUT

Enable High-Density Robots (Multi-Robot Execution)

If running multiple automations on the same machine, enable high-density robots:

  1. Go to Orchestrator → Tenant → Settings.

  2. Enable High-Density Robots.

  3. Configure multiple user sessions (RDP users) on the machine.

Regards,
Arivu

3

@BrianaB

You can run multiple backgroung process along with one foreground process only if you are running in attended mode

The image provides information on running attended automations in the background, explaining that attended automations operate under human supervision and background execution allows multiple automations without UI interaction. (Captioned by AI)
The image provides information on running attended automations in the background, explaining that attended automations operate under human supervision and background execution allows multiple automations without UI interaction. (Captioned by AI)873Ă—433 42.5 KB

If you are running unattended - Multiple license needs to be allocated to the machine

The image explains that unattended automations operate in the background without user interaction or supervision, typically within a Windows session under the Local Service, and may face issues with Microsoft applications, requiring individual licenses for multiple simultaneous automations. (Captioned by AI)
The image explains that unattended automations operate in the background without user interaction or supervision, typically within a Windows session under the Local Service, and may face issues with Microsoft applications, requiring individual licenses for multiple simultaneous automations. (Captioned by AI)886Ă—438 42.5 KB

For more details, Refer: Robot - Background automations

1 Like
4

Hi @BrianaB

Ensure the background process runs on a modern folder with unattended robots enabled.

Set the process to run under NT AUTHORITY\LOCAL SERVICE by configuring it in Orchestrator > Robot Settings.

Enable “Run in Parallel” for unattended robots in Orchestrator > Tenant > Settings.

Use a dedicated unattended bot to ensure it always runs without waiting for other jobs.

Check below thread,

5

This is true on Attended license only. With Unattended license, you will have to assign additional license to run the bot.

6

Hello, there is no setting for High-Density Robots under Tenant → Settings

7

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.