previously when one process is running and if i run another process then it goes to pending state. but now its faulted with this error "A foreground process is already running. Only one foreground process can run at a time " .
I am using unattended bot to trigger the process and i use community edition.
How to overcome from this?
Its weird. Did you change anything recently ?
hi @lakshman
previously i use attended bot to trigger the process. But now i use unattended bot to trigger the process.
Are you running both processes in same or different machine ?
@lakshman
same machine
Then it should go to pending state only.
Do one thing create one small process with Message box activity and publish it into Orchestrator. And then check it whether it is giving same error or not.
@lakshman
ok
hi @lakshman
i try this.
i started the process with message box then i run another process.
And result is same that another process fails.
hi @lakshman
what can i do to overcome this issue?
@loginerror @Pablito @Lahiru.Fernando
Do you have any idea why it’s giving this kind of error ?
I tried this again in my Orchestrator, and it is giving the expected (one is running and one is pending) scenario
It should not throw the error…
My robot type is set to Unattended and I executed the two processes from the Processes screen in the Orchestrator.
Can you show us how you configured your robot? just to get an idea…
That’s weird…
Can you try this. Can you disconnect your robot from the orchestrator, and set it up again, and try…
hi @Lahiru.Fernando
i try it bot the same error occurs again
Is the machine maybe configured with multiple runtimes?
hi @loginerror
no. only one machine is configured.
Hi @Lahiru.Fernando
can you please try to run the two processes through Assistant. And check it what the state shows.
HI @arijit1213
Nice spotting… You are correct…
It gives the error when starting through the Assistant…
Yes it will give error when we will try to run it from Uipath Assistant as we can run one foreground process at a time but not getting why it is throwing this error when we run it from Orchestrator.