WorkingTasks by 0 sec

lukasadrian

Windows 10, all updates
WorkingHours Version 2.65.10.0
Its Pro and sync on GDrive.

Hi, my time tracking shows a lot of '0 sec' in the list.
Yesterday I pressed instead Stop Pause and later I filtered some data on mobile WH. Just filter and then turned if off.

Today in the morning I checked WH on my windows and since the 14th July is everyday one WorkingTask has 0 sec.
I remember that in the mobile app in the fiter section the time stamp was set from 14th July to 23rd July, the same time period like my broken working tasks.

In your DB (WorkUnitTags) the entries are also wrong (see screenshot, still repeating the same entry and the times are wrong).
It looks like all entries from ID 372 are wrong. The start time is the 13th July but it should be the 23rd July. Maybe the synchronization with my mobile phone was not working.
I don't touch the data, will waiting for your response.

I see there are some backups bei GDrive, can I use them? What I should do Timo?

Thanks and regards,

Lukas

timo

lukasadrian Yesterday I pressed instead Stop Pause and later I filtered some data on mobile WH. Just filter and then turned if off.

I didn't understand that part.

0 sec work units like in your screenshot can happen when you start + pause a work unit and then stop the work unit a few days after. As the timer was paused, the app creates 0sec work units to indicate that the timer was active, but not running on those days.

If you think this wasn't the cause, please describe me how I can reproduce this so I can have a closer look.

lukasadrian I see there are some backups bei GDrive, can I use them? What I should do Timo?

Of course you can use/import backups in your GDrive, WorkingHours creates them on a daily basis

lukasadrian

Hi TImo,

On the 23rd I was working on my computer and WH was on. After my work I pressed on Pause instead of Stop and turned my computer off.
I went to my Cellphone and wanted to check something by the mobile Version of WH (Android). I start to filter some tasks. I saw that the date was set from the 14th July in my filter. After filtering I turned off my phone. It was all on the same day. But I don't know if my phone was already up to date with the GDrive-Data. Sometime you have to wait few seconds.
On the next day on 24th I start WH on my computer and saw that problem.
I mentioned the date 14th on my phone because all entries on my Windows from the 14th are wrong. There is overall the same entry. That special entry has to be just on the 13rd July. Now that entry it is overall in that time period from 14th until 24th but with 0 sec.
Why it was set to 14th July I really don’t know, maybe I used WH last time on the 14th on my phone.

It sounds simple but I think that case was an exception. I never had problems with WH.

Hope you understand it now. My English is not so perfect.

Good with the backup, I will try it.

Thanks Timo!

Lukas

lukasadrian

After import of the 23rd backup all looks maybe good, have to check is something is lost. But no 0 sec any more.
But I see the timer is on Pause.
If I press Stop that special entry will be add overall until today. The reason is that the active entry on the 13rd and not the last one. Is still active and set to Pause, see the screenshot.
And that entry is also twice at that day.

As I mentioned, I never had problems with WH. I don't touch it now, maybe you want some data or something. Will wait for your response.

timo

That looks like at some point the sync wasn't able to happen quickly enough before PC shutdown or similar and then at a later point, WorkingHours had to merge 2 databases, in which case it is possible that duplicates happen (because it cannot decide which version is the newer one). That is the duplicate you can see in your last screenshot, one of which is a still active timer which, when stopped, can cause the 0sec entries that I explained in my first response.

lukasadrian

Hi Timo, sounds logic. I think that is really seldon and hard to reproduce. But next time you know why it happened 😉

The help with the backup was good, now I can continue the work with WH.

Thanks and regards,

Lukas