Efficiently Scheduling Multiple Month-End Processes on Orchestrator

Help Orchestrator
, ,
1

Hi everyone,

I’m managing multiple month-end processes on a single VM with one unattended bot in UiPath Orchestrator. We have processes A, B, and C that need to run efficiently. Given the constraints of a single bot, I’m looking for the best way to schedule and manage these processes without wasting resources.

Could you share any strategies or best practices for optimizing bot usage and scheduling under these conditions?

Thank you!

2

Hi @ImPratham45

As per my knowledge,

Prioritize tasks by setting SLAs, stagger the start times of processes A, B, and C to avoid overlaps, optimize each process to reduce runtime, use process dependencies to ensure sequential execution, and continuously monitor bot performance to adjust schedules based on runtime analytics.

Happy Automation

3

@ImPratham45
if you have any prioritization set the priority for your processes.

If it time based trigger, you can trigger it every one hour any specific time. or if it is queue based trigger then you no need to do anything.

4

Hi,

Thanks for your input! The challenge is that the number of transactions can vary significantly—sometimes we get 1 or 2, and other times up to 35, with each taking around 7-8 minutes. Occasionally, there may be none. This variability makes it tricky to schedule efficiently.

5

Hi,

Thanks for the suggestion! If we set a time-based trigger (e.g., every hour) and there’s no data for A and B while C has 10 transactions, the bot could end up being idle for around 2 hours before checking on C.

This idle time is what we’re trying to minimize. Any advice on managing such situations efficiently?

6

If it transactional process use queue based trigger

7

Indeed, @ImPratham45

Use Orchestrator triggers to start processes based on queue size. Set dynamic scheduling to trigger processes when transactions are available, prioritize tasks based on urgency, and break larger transaction sets into smaller batches for efficiency (Optional). If no transactions are present, let the bot remain idle to conserve resources.

Happy Automation…

8

Would be useful if you could share some details around the processes:

  1. How are they triggered currently (Email, File, etc)?
  2. Are you using Dispatchers and Performers?
  3. Is there a priority order for the Processes?

Event-Based triggers using the Integration Service can be quite useful instead of having a Dispatcher looking and checking for information.

Replacing Dispatchers completely if you can send an API call directly from another system and have Queue-Based Triggers configured.