Can UiPath Runtimes Be Utilized Based on Execution Hours Instead of Fixed Concurrency?

We currently have 5 unattended runtimes/servers but more than 50 automations competing for execution during business hours.

The challenge is:

  • Many automations require execution within a limited daytime window
  • We can execute only 5 automations concurrently
  • Due to runtime limitations, some priority processes are delayed beyond their required execution window

Our question is NOT about extending or violating licensing limits.

We want to understand:

  1. Whether UiPath supports any execution-capacity model based on cumulative runtime hours instead of fixed concurrent runtimes
  2. Whether unused runtime capacity outside business hours can somehow be leveraged during peak daytime load
  3. Best practices for handling large automation volumes with limited unattended runtimes
  4. Recommendations around orchestration, queue-based execution, workload balancing, or runtime optimization

Example:
If a runtime is used only 10–11 hours/day, can the unused remaining time capacity be redistributed in any supported way across additional servers/machines during peak hours?

Or is UiPath licensing strictly limited by concurrent runtime count regardless of total runtime hours consumed?

@Vinodkumar_Kalkumbe

Unfortunately no option as such as if now but if you can utilise Serverless robot which can help you dynamic workload balancing.

@Vinodkumar_Kalkumbe

In UiPath licensing, unattended automation capacity is fundamentally based on concurrent runtime availability, not cumulative runtime hours consumed over a day.

Happy Automation