Dynamic Trigger based on queue count in Orchestrator

Help Orchestrator
1

I have a Performer where it is currently launched by a queue-trigger (with Max concurrent jobs = 2), but when the queue spikes (e.g., >700 items), those two jobs can’t burn down the backlog quickly enough. Users then end up manually starting extra jobs after checking queue counts. Is there any way to achieve this dynamically by monitoring the queues count?

1 Like
2

Hi @adarsh_kotagiri

In UiPath Orchestrator there’s no built-in way to automatically increase the number of running jobs based on queue item count. Max concurrent jobs is static per trigger, so Orchestrator won’t “auto-scale” jobs when the queue spikes.

  • Increase Max concurrent jobs permanently to a safe upper limit
  • Create a separate monitoring process (or API script) that checks queue counts and starts extra jobs via Orchestrator API when thresholds are crossed
  • Use multiple triggers tied to different schedules or queues
  • If on Automation Cloud, scale the robot VM resources so higher concurrency is possible

So yes, it can be done, but only via custom logic using Orchestrator APIs or an external monitor not out of the box.

1 Like
3

Hi @adarsh_kotagiri

No — UiPath queue triggers cannot scale dynamically based on queue count.

  • Increase Max Concurrent Jobs in the queue trigger (static limit).
  • Add a Time Trigger alongside the queue trigger to start additional jobs periodically during spikes.
  • Use an Orchestrator API / monitoring process (separate bot) to:
    • Check queue count
    • Start additional jobs programmatically when thresholds (e.g., >700 items) are exceeded.
  • Use multiple queues or multiple processes to distribute load.

:backhand_index_pointing_right: UiPath does not currently support auto-scaling jobs purely based on queue size like an elastic worker pool.

1 Like
4

@adarsh_kotagiri

There is no direct way, but a slight modification in your process can achieve this

in get transaction item state in your REF(if not ref then before getting queue items)

  1. use get processes and get the current number of running ot pending jobs..use if condition after that to check if the max job count is reached for now say 5
  2. in the then side as max jobs is reached do nothing
  3. on else side get the queue items count which are in new state..if the number is >500 or 700 any count you want to check then start a new job else continue with the process

this ensures dynamic logic is present with minimal steps

cheers

1 Like
5

Hi @adarsh_kotagiri

No. UiPath Orchestrator does not support dynamic scaling of queue-triggered jobs based on queue item count.
I think , the only supported options are increasing max concurrent jobs on the queue trigger, adding more robots/machines, or using external orchestration (API/alerts) to start additional jobs manually or via scheduled triggers.

Happy Automation

1 Like
6

Hey, Thank you @Anil_G, I will follow this approach.

1 Like
7

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.