This is a bug in the generation of results of scheduled queries in osquery-perf. It seems the bug has been around since we added scheduled query result support in osquery-perf. PS: In my Fleet downtime tests for https://github.com/fleetdm/fleet/issues/16423 I probably missed this because I was using a high frequency queries (150s intervals IIRC).