What can cause hourly breakdown to be empty?

[leverglowh]

So it's happened only twice, last Friday and today. Weirdly Monday is fine..
When I go to the daily summary of these two days, I get correct total time and heartbeats and projects breakdown, but hourly chart shows "No data".

I was using wakapi:latest docker image (docker inspect shows create date January 2026) with no issues until now.
While trying to understand what the issue can be, I upgraded the image to ghcr.io/muety/wakapi:latest, but the result did not change :(

I tried checking the DB (Postgres).. Using these simple selects

select * from durations d where d."time" >= '2026-04-28T00:00:00' and d."time" < '2026-04-29T00:00:00';
select count(*) from heartbeats h where h."time" >= '2026-04-28T00:00:00' and h."time" < '2026-04-29T00:00:00';

For 4/24 I got 245 rows in durations and 598 rows in heartbeats, no hourly breakdown
For 4/28 I got only one row in duration, with value 55332000000, category ai coding, entity copilot xxx, and 580 heartbeats
Any idea how I can debug this?

The only duration being copilot makes wonder if a stuck copilot session can break it?

I've enabled wakatime logging (although I use vscode most of the time) now, maybe it can help in the future..

[muety]

Sorry for the late reply!

For 4/24 the situation is clear. We have this check in place that checks if the number of individual durations is greater than 200, the chart won't render for performance reasons and because you couldn't make much sense of it anyway. I'm aware that this is somewhat less than perfect and rather just a workaround. Ideally, the chart would support scrolling and zooming and accordingly only request parts of the data of even different aggregation levels (think downsampling or sth.). I might get to implement something like that at some point, but for now it's not a prio tbh.

For 4/28 it's strange. I can't see how this situation of having just one ig duration could come about. Would you mind sending me a (optionally pseudonymized) excerpt of your database's heartbeats table for that day? That would probably help me debug this issue.

[leverglowh]

Hi muety!
Thank you for the reply!
I understand the 200 rows check, and it being low priority.

For the single row issue.. Is there a delay in updating the durations table?
I was running those select queries 4/28 at 7 PM GMT+2, and got 1 row, but today I went back and checked, and I got 320 rows.

Got same issue on today's dashboard as well.
It's 5/15 8 PM GMT+2 right now and duration for today also shows just 1 row, with 307 rows of heartbeats.
I'm thinking maybe I actually went over the 200 threshold for today causing empty chart, but the DB is just not updated yet?

I can get you an export of heartbeats, if it can help, but I don't think it's relevant anymore.

[muety]

There's no "delay" on Wakapi's end, but the CLI only sends heartbeats in batches every now and then. You can use the following commands to check how many heartbeats are waiting to be uploaded and forcibly push them:

~/.wakatime/wakatime-cli --offline-count
~/.wakatime/wakatime-cli --sync-offline-activity 0