Background Process template vs Normal RE-Framework Template

[gabi_verzea (Gabriel Verzea)]

@Scott_Taylor

round Process is a template for creating processes that can run in parallel on the same Robot, together with one foreground process. For this reason, background processes must not contain activities that require user interaction."
Question is, what if I want to trigger the same background pro

I had the same question posted in another thread. I investigated it more and I think I found the answer why it runs in parallel from Studio or the Assistant, but not scheduled from Orchestrator (where it is pending). Here is the thread with the explanation:

Run two background processes in parallel, triggered from Orchestrator

Hi guys, I am testing the running of parallel of two background processes, from Orchestrator. I have two different background processes, with a 30 sec delay and a log message activity. Running them from the Agent is no problem, they run in parallel, and I can also see both of them running in parallel in Orchestrator, after I start them from the Agent. But when I start the run from Orchestrator via the Run Process button, the second one waits in pending mode for the first to finish. So they do…

And I have also created a video showing what settings must be changed to convert a standard REFramework to a Background Framework - you can navigate directly to that section of the video with the chapters in the description of the video (minute 18:59). Hope this helps:

Hacking the UiPath RE-Framework | Advanced Tutorial | Non-queue, non-repetitive and background