2 years ago
A new way to handle long running VMs
Historically it's been very difficult to determine when a virtual machine should be shut down. The shutdown policy associated with the environment only takes effect when the user session is idle. Determining true idle states across all browsers has proven to be unreliable, thus causing VMs to run longer than customers expect.
We have now moved the ability to prevent VM shutdown to outside of the policy. The Policy Details page now allows a maximum running period of 12 hours.
To allow a VM to run constantly, this now needs to be specified on the VM within a template or environment via a row action called 'Disable auto-suspend'.
Any VM without this setting will automatically be shut down after 12 hours, regardless of user status.