@NobodyNada Thanks. It acted basically the same as it had previously: just stopping and then some typical MS connection issues (hours after stopping). It may have been
responsive to a !!/reboot
. The previous time it didn't appear to respond until I logged in to the instance (and only logged in). I'm not sure what's causing this, but we can put in a detection to automatically reboot when something similar happens.