Mismatched VM States Between Cloud Platform and CLOUD TOGGLE

There might be occasions where the state of a VM in CLOUD TOGGLE is different to the state shown for it in Azure or AWS. When this happens it is usually because a VM has had its state changed in the cloud platform (Azure or AWS) instead of through the CLOUD TOGGLE interface. Due to the underlying mechanics of each integration, it is normally the case that for AWS VM’s the state will change to reflect the actual state in AWS very quickly - within a couple of minutes or less. For Azure VM’s however, this can take significantly longer.

If there are VM’s that are not in the same state that is showing in Azure (such as showing as powered off in CLOUD TOGGLE when, in Azure, they are running), this can be rectified by clicking on the Refresh Servers button on the Manage Servers page in CLOUD TOGGLE.

To avoid this behaviour, it is always recommended that wherever possible VM states are changed directly in CLOUD TOGGLE.