Run only one job at a time

Hello. I am using attended robots(comunity version )and I need to know how can I run only one job at a time.

@RS_App

  1. Orchestrator Environment Configuration:
  • Open UiPath Orchestrator.
  • Navigate to the environment where your robot is configured.
  • Edit the environment and set “Number of Robots to Execute” to 1.
  1. Process Configuration:
  • In Orchestrator, go to the Processes page.
  • Edit the process you want to control.
  • Set “Maximum Number of Robots” to 1.
  1. (Optional) Queue Configuration:
  • If using queues, set “Max Concurrent Jobs” to 1 in the queue settings.
  1. (Optional) Robot Configuration:
  • In UiPath Assistant or Orchestrator, configure the robot to allow only one concurrent job by setting “Number of Concurrent Jobs” to 1.
  1. Publish and Apply Changes:
  • In UiPath Studio, publish your process.
  • Update the process in Orchestrator.
  • Ensure your changes are applied by checking the environment, process, and optional settings.

Hi @RS_App ,

To ensure that only one job runs at a time in UiPath with attended robots (community version), you can utilize the Queue feature. Create a queue and assign the job(s) to it. Then, configure the robot to fetch the items from the queue one at a time, ensuring only one job is processed at any given time. This way, the robot will wait for the completion of a job before starting the next one.

Thanks,

Hello.
Could you provide more specific descriptions? I couldn’t find any of them.
Thank you.

If you are running an attended robot why can’t you just start a job only when you want it to?

I am using UiPath apps. I trigger a process from the app, and if the user clicks a button that triggers a second process before the first process has ended, two processes are running, causing a problem for the application.

But you are the user. Just wait until its finished to do it?

You should have full control over the attended robot, since you are the only user.

I am not the only user.

Can you explain your use case then, this doesn’t make sense in the context of a Community licence?

You have two ‘Attended - Named User’ licenses and one ‘Automation Developer - Named User’ license, so you can have three attended robots on one cloud.

Ah true,

They offer more licences in Community than they used to, and more basic users.
My apologies.

I’m still not really understanding where the issue is though? I assume you are just using the attended robot to test this all works, in a real environment you can use an unattended robot? Otherwise why are you using an attended licence for automations triggered by someone else?

Is my assumption wrong? If so what is your use case / need?