Exception: A foreground process is already running. Only one foreground process can run at a time

Feedback Robot
1

Hello,

In our organization we recently updated UiPath Robot to 2021.4.5 in order to fix the issue mentioned in the title of this topic 2021.4.5 (uipath.com)

Unfortunately, we are still experiencing the issue when multiple jobs are started on the same robot (I have replaced the name of our processes, robots and machines for confidentiality reasons).

Process: ProcessA
Environment:
Robot: robot02
Machine name: MachineA
Info: A foreground process is already running. Only one foreground process can run at a time.

RemoteException wrapping System.InvalidOperationException: A foreground process is already running. Only one foreground process can run at a time.
at UiPath.Service.Job.Start(IUserCredential credential)
Start Time: 10/27/2021 10:01:51 AM
End Time: 10/27/2021 10:01:52 AM

Process: ProcessB
Environment:
Robot: robot02
Machine name: MachineA
Info: A foreground process is already running. Only one foreground process can run at a time.

RemoteException wrapping System.InvalidOperationException: A foreground process is already running. Only one foreground process can run at a time.
at UiPath.Service.Job.Start(IUserCredential credential)
Start Time: 10/27/2021 10:01:52 AM
End Time: 10/27/2021 10:01:53 AM

Process: ProcessC
Environment:
Robot: robot02
Machine name: MachineA
Info: A foreground process is already running. Only one foreground process can run at a time.

RemoteException wrapping System.InvalidOperationException: A foreground process is already running. Only one foreground process can run at a time.
at UiPath.Service.Job.Start(IUserCredential credential)
Start Time: 10/27/2021 10:01:53 AM
End Time: 10/27/2021 10:01:53 AM

Has the error only been partially fixed?

3

this is only when there is a process already running

in your task manager check if any process was triggered in your machine

you can kill all instances of robot there and open new

4

Yes, I’m fully aware of the fact that the error only occurs when a job is already running and a new job is started.
However, successive jobs should simply wait in “Pending” state. This is the behavior that we experience the vast amount of time, yet on occasion we still experience the error above.

5

Check the settings for each Robot. Are they set to log into console? Not sure why it would cause this to happen, or if it even would, but just a thought. Something to check.

6

Login To Console is set to “No”.

7

Are you starting the processes from Orchestrator? If yes, then they should be queued. If they are not, then we have a problem :sweat_smile:

If you’re starting the processes from CMD or Assistant, then it is considered an attended use case and the behavior is the expected one.

1 Like
9

Processes are started from Orchestrator. We are still experiencing the error, although it seems to be occurring less frequently.

10

We experience this problem too. Jobs started from Orchestrator v 21.10 .

Generally we see this error for the processes that have High priority.

12

We’re having the same issue using Cloud Orchestrator and 21.4 robots.

Processes are unattended and triggered by a Queue trigger. Multiple jobs are triggered for the dispatcher/performer processes related to Document Understanding.

13

Same problem here.
We have Orchestrator 2020.4.3

Can it happen if Orchestrator starts a new pending process too fast, so the VD doesn’t really have the time to log off?
Or can it be VD remote access settings?

Vote this topic guys.

14

It is a bit hard to reproduce.

I would suggest two courses of action:

  • in case of an Enterprise license, please contact our technical support for our team to be able to directly investigate the issue:
    Contact Technical Support
  • in case of a Community License, it would be great if you could try to reproduce the scenario with clear steps, which would help us better diagnose the issue
  • lastly, an upgrade to the latest version could be considered as a last resort
15

Hi @hbpe,

Did you get the solution for this issue?

Thanks,
Shreyash

16

Hello,

I don’t think we have experienced the error for the past several months. Updating Studio and Assistant beyond version 2021.4.5 might have fixed the issue.

For reference, we are currently running 2022.4.3.