After the 5.5 update I am seeing only on some Hyper-V clusters the error Exception and not Succeeded after a VM move or size up/down. I have checked and these still discover and validate with no errors. In the optimization summary, when a VM needs to move, VMturbo thinks it moved it but no actions were performed in the cluster. I have also tried to remove the hosts and readd with the same results. We have SCVMM in vmturbo as well.