Hello Brian,
The issue was indeed caused by overflow. In fact, it’s been overflowing (consistently) from the start and this overflow issue only became apparent after long suspensions. A time_t value was wrongly assumed to be 64-bit in the code. We just fixed it today. We also modified it to be unaffected by clock changes. So, now this function should never go backwards. Huzzah!
The fix will be made available in the next daily build, which is available to you if you are a paid subscriber. Keep a look out for daily build release notes stating fixes in system.getTimer().
Again, thanks for your help! Your test results helped us narrow down the issue. [import]uid: 32256 topic_id: 14768 reply_id: 54787[/import]