VM Setup Question on Availability Settings

Help Orchestrator
,
1

Hi! I’m setting a VM in Orchestrator and looking at the availability settings. If the VM is idle and shuts off, will it automatically reboot for when the next automation is scheduled? What’s the disadvantage of having it set to “Fast” availability vs. “Always”?

2

The availability settings for a VM determine how it behaves when it’s not in use.
Fast Availability: The VM is shut down when idle, but it boots up quickly when a job is scheduled for execution.
Always Availability: The VM remains continuously running regardless of whether it’s being used or idle.
The disadvantage of having the VM set to “Fast availability” is the potential delay caused by the VM booting up when a scheduled automation job needs to run. Conversely, the “Always availability” setting maintains immediate readiness but may lead to increased resource consumption and cost if the VM remains running even when not actively used.

3

Hey Viroop. Does it reboot on it’s own? In your experience has it ever gotten stuck booting up due to things like security updates that delay the automation by more than 5 minutes? I’m now looking at the Balanced setting since I could then use the machine setup with more RAM.

4

Yes, It does reboot on its own. However, the challenges persists. It always depends on how compliance works at ones organization. In my experience, Although we had scheduled VM reboots, when ever there are emergency patches, the bot would face errors due to the reboot pop-up on screen. In such cases we have to closely work with VM team and make sure to set up ground rules on the VM used for RPA. As far as I have seen, VM would be back within 5 minutes and never seen much issues as our VMs are procured from Azure.
If you running 24/7 automations, you can always set it to “Fast availability”.

5

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