Orchestrator does not work more than two pending

[sera]

Why when the orchestrator is working more than two pending?

[Rammohan91 (Rammohan Banda)]

Could you please elaborate your question with detailed description, screenshots and steps to reproduce if possible? It would really help community members to guide you with a proper solution.

Have a looks at this,

How to ask a good question?

Please also have a look at our updated Forum FAQ here Without further ado: Before you ask… Community forum is not a helpdesk Let’s put this in the front - vast majority of people here do not work for UiPath. We’re volunteering our free time to help others and as much as it pains to say it, not all topics might get a satisfying answer. If you’re an enterprise customer and need an answer from UiPath support, send them a ticket through the form or via their helpdesk portal. Did you search? C…

Thanks,
Rammohan B.

[EricC (Eric)]

Hi Sera,

I didn’t fully understand your question

I think this thread will be useful
You can only have one job pending per Process+Robot

Only one job in pending state

https://demo.uipath.com/odata/Jobs/UiPath.Server.Configuration.OData.StartJobs I have created job using above api url and it is in pending state. immediately again i tried to create new job its not creating.Is maximum only one job allowed in pending state? Please help

You may want to look into other ways of ensuring your process continues running if that is the purpose of queuing up processes

Cheers,

[ivandiaz]

There is a valid use case for this since UiPath orchestrator now supports input parameters at the process level… Example: If you want to get data from a system with multiple tenants, a clean way is to create single dispatcher process that is configurable rather than copy the package, rename package and republish the renamed package.

If a running process takes long and 2 schedules of your process are launched with different configurations, then the 2nd schedule will be killed.