We found that one of the billable usage aggregates that had messages from swatch-2406 contained billable_usages with snapshotDates for 3/27/2024 but the aggregate was consumed by swatch-producer-azure on 4/1/2024 instead of the same day. We need to investigate why this took so long to be consumed or published by kstreams.

Update:
This was caused by certain partitions of the billable-usage-aggregate topic not getting messages which means the suppressed messages got stuck. In order to fix this I implemented a cron job that will push a "flush" message to each partition of the topic every hour.