If two foreground processes are triggered does this error or set one job pending

We have one robot that does a foreground process (A) on a schedule, but lets say we also want it to run another foreground process (B) to work whenever things land in a queue (i.e. set up a trigger on that queue) - we don’t care if the the user of (B) has to wait sometimes for (A) if it happens to be running.

Does orchestrator:

(1) Work out that (A) is running and is foreground process, and so schedule the process (B) behind it, if its triggered … i,e. it creates a new job but in pending state.

(2) Starts a job for process (B) the moment it is triggered by an incoming queue item, but then errors that job with ‘Bot fails due to a foreground process already running’ because (A) is still running.

If (2) what is the best way to go about achieving my ambition with a single robot?

Hello @andrew.pate!

It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.

First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.

You can check out some of our resources directly, see below:

  1. Always search first. It is the best way to quickly find your answer. Check out the image icon for that.
    Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

  2. Topic that contains most common solutions with example project files can be found here.

  3. Read our official documentation where you can find a lot of information and instructions about each of our products:

  4. Watch the videos on our official YouTube channel for more visual tutorials.

  5. Meet us and our users on our Community Slack and ask your question there.

Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.

Thank you for helping us build our UiPath Community!

Cheers from your friendly
Forum_Staff