If an employee is using Hubstaff and their computer crashes, what are the chances a record of their progress for that session is lost?
An abrupt shutdown (i.e. power outage while or force shutting down the app via task manager while tracking) may cause a halt to a computer, causing the desktop client to crash or not quit properly. Consequently, when you restart the client, we detect you as idle as no activity was being tracked, and resume tracking because the timer was never stopped manually upon restart. Since the transient information collected about your activity levels was lost due to a possible abrupt power outage, which results in the desktop app quitting abnormally and the time that it took to restart during which it would be impossible for us to track activity, there is no option but to report the time as ‘0’ activity (idle in this case)
It’s all a matter of how we present the information. Idle time should be reported as idle time, not ‘0’ activity, as they are not equivalent. Idle time is a specific definition (subset) of activity in which we have determined based on the configuration that the employer wishes to treat X consecutive seconds of ‘0’ activity as ‘Idle’. In this case we did not make that determination, we simply reported what we knew to definitively occur.
Linux users in a Pantheon environment will still log time with 0% activity. The desktop app will auto-resume as if it was powered off suddenly, even if you do quit the app correctly.