Hi @jackoffer, we implemented a fix for the issue with temporary timestamp skew upon resuming a suspended Machine, the system clock is now synchronized immediately on resume. You may need to re-deploy your Machine in order for the updated code to take effect. Let me know if this resolves your issue!