no one has experienced this?
Can you please check the KB: https://kb.vmware.com/s/article/2112843. Even though it is related to 5.x, you could see the recommendations as best practises.
Check the vmware.log file of the VM to find any related logs after the change in the status to understand what is causing this behaviour.
The rules may getting disabled due to some other rules dominance( possible). check from storage end for any specific rules which may cause this.