Working Hours 2.9.28 Big Sur does not track after midnight

StevenRohr

Work hours is showing zero hours for following day if time tracking is started before midnight and ends after midnight.

Worked properly with prior releases.

timo

Unable to reproduce this. I also don't know what could have changed.
Also, where exactly does it show zero hours? The timeline view? The menu item? The Excel sheet? The Analytics screen?
Please explain in more detail & illustrate the problem with screenshots

Peter Paetzi

Today I had the same problem.
I started recording on the iPhone before midnight and stopped on the Macbook after midnight.
In the overview I saw the correct working time (00:00 - 00:29), but the summery shows 0 minutes.

timo

When exactly did you start the work unit and what does the work unit before midnight show? Perhaps you have paused the work unit at some point?

stevel

Also seeing this bug on Android, version 2.9.43. The bug appears when doing an Excel export. Work units are split over midnight as expected but the work unit after midnight has 0 duration and a break time equal to the duration. See the image below.

timo

Do you mean the export shows different data than what is shown in the app?
If you pause the timer a work unit that goes over midnight, the app currently cannot tell when exactly you did pause it (before or after midnight) and then puts as much time as possible in the day before midnight and the rest after midnight. In other words, the app doesn't store the timestamps of when the timer is paused and resumed. In sum, there should be no "work duration" being added or removed

stevel

The export shows the same data that is shown on the Time Tracking screen. The unit after midnight has a duration of 0 seconds.

It is a pity the pause button does not actually work properly in these circumstances.

Danielle

Hi - I am seeing the same issue here. Mac OS Venture 13.5.2. When timer starts before midnight and carries on past midnight, the portion after midnight shows the correct minutes / time recorded but the total amount is recording as 0 seconds.

I have settings so it pauses/restarts automatically if no activity - but this occurs even when I've been actively using the system so not pausing.

It used to work fine for years but noticed this started happening in last few months - not sure when exactly but it does seem to be a recent bug.

Thanks

timo

Danielle Does the problem also happen when you manually create a work unit that is equally long (has the same start/end time) as the one that was automatically started/stopped by the idle detection feature? I need a way to reproduce this or at least something to narrow it down. If we know this only happens in combination with the idle detection feature, this would be a start

Danielle

Hey Timo, I've just manually added a couple of different work units which span from 11pm until 1am next day (for example) and they calculate correctly, so looks like it's linked more to when there's an automatic start/stop or when the start and stop are on the two days. I'll do a bit more testing for you as soon as I can to leave it running around midnight to see if I can see any more patterns and I'll let you know! Thanks, Danielle.

Danielle

Hey again Timo - think I've got something a bit more useful now.

When the work unit goes past midnight (whether or not it goes idle during that time doesn't seem to matter), and I click 'Stop' during the same session, it seems to work correctly.

However if the computer goes to sleep during a session - for example I close the lid without manually 'Stopping' the timer, then the next time it's opened up, the Idle kicks in and the timer starts counting again - but when I click 'Stop', everything past Midnight is counted as Zero seconds (even though the minutes will be, say, 00:00 - 10:00, and even if there had been activity during that time).

Let me know if that helps / if anything else I can try out to help.
thanks,
Danielle