{"version":"2.1.223","anchor":"stats-cache-watermark-ahead-of-today-no-longer-triggers-a-re","canonical_anchor":"stats-cache-watermark-ahead-of-today-no-longer-triggers-a-re","heading":"Stats cache: watermark ahead of today no longer triggers a rebuild","tier":"notice","area":"Usage & Limits","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/stats-cache-watermark-ahead-of-today-no-longer-triggers-a-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Stats cache: watermark ahead of today no longer triggers a rebuild\n\nA clock skewed ahead no longer forces your token stats to rebuild on every run.\n\n**What**\n\nClock skew that leaves the cache watermark in the future no longer forces a daily token rebuild on every run.\n\n**Details**\n\n- The rebuild is skipped when the cache's `lastComputedDate` is ahead of today, with a debug log explaining why.\n- Incremental writes now also count `dailyModelTokens` when deciding whether anything actually changed.\n\n**Evidence**\n\n`; skipping the dailyModelTokens rebuild until the clock catches up`\n\n- Area: Usage & Limits\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}