{"version":"2.1.281","anchor":"freshness-check-tolerates-a-clock-that-jumps-backwards","canonical_anchor":"freshness-check-tolerates-a-clock-that-jumps-backwards","heading":"Freshness check tolerates a clock that jumps backwards","tier":"internal","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/freshness-check-tolerates-a-clock-that-jumps-backwards","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Freshness check tolerates a clock that jumps backwards\n\nA recency check no longer fails outright when the system clock jumps backwards\n\n**Unclear.** The finding does not say which feature relies on this recency check.\n\n**What**\n\nClaude Code has an internal check that decides whether something happened recently. If the computer's clock jumps backwards, the time elapsed can come out negative. Before, the check then answered \"not recent.\" Now it only checks that the recorded time is not later than the current time. The check can also be given a different clock to use, which makes it easier to test.\n\n**Why**\n\nA clock correction, such as a time sync or a change of time zone setting, should no longer make something that just happened count as stale.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}