So I did leave my desktop off for the whole night until now. The problem is half resolved, because as soon as I checked ActivityWatch for today (September 12) I immediately saw new activity building up on the Activity tab. Then I went back a day… and no, it still doesn’t show any activity for all of Sept. 11. I even went back to Sept. 10 and it’s still not being counted as data under that date (which I guess is actually good, it means that the program knows well enough not to taint one day’s data with another even in a situation like this).
Here is just a picture of my overview on the Timeline tab:
Two things jump out: 1) There are clearly items that were tracked for Sept. 11 and 2) something seems kind of wacky about how the not-afk status was reported. The timestamp on that bar says 2020-09-10T9:18:52-04:00 but it’s also saying that this block of time accounts for 32h 10m 10s of time. From looking at my laptop, it seems like it is somehow able to correctly sense the passing of the day mark and so will chop afk statuses at that time and start a new block.
Upon seeing this happen, I went back and looked at some older data:
So you’ll see, over on Sept. 3 I had another not-afk block happen that started at 10:33 (whenever I turned on my computer for that day) that lasted for 48h 50m 4s. This means it easily stretches into Sept. 4 and Sept. 5. I had originally thought that the data was reported for these days, but it turns out that when looking back there’s nothning on the activity tabs. Sept. 11 also shown for clarity.
It should be noted that Sept. 3, Sept. 6, Sept. 10, and Sept. 12 (the adjacent days) all display data normally. The specific items reported in the timeline also show up on the weekly summary on the Activity tab. But for some reason, probably because of this overflow from one day to the next of the not-afk status, it seems unable to parse out the items for days after that overflow begins.
So obviously, the answer here seems to be either to reduce my afk timeout again (which I would rather not do) and/or to shut off my computer when I am done using it at a set period of time especially close to the day cutoff (which I probably will start doing more frequently). However I would also like to know if there are any other ways I could fix this, or if this is even something I have to report as an issue on the Github or something?
Any help or insight would be appreciated, thanks 