{"version":"2.1.299","anchor":"rewind-expiry-checks-use-service-side-time-and-emit-telemetr","canonical_anchor":"rewind-expiry-checks-use-service-side-time-and-emit-telemetr","heading":"Rewind can be refused when a server-set deadline passes","tier":"notice","area":"Sessions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/rewind-expiry-checks-use-service-side-time-and-emit-telemetr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Rewind can be refused when a server-set deadline passes\n\nRewind now checks a server-provided deadline against the service's clock instead of only looking at how old the conversation is\n\n**What**\n\nRewind takes a conversation back to an earlier point. Claude Code used to decide whether a conversation was too old to rewind only from how long ago it was saved. It now compares a deadline against the service's clock, or against the time of the conversation's most recent part if that clock is not available. If the deadline has passed, the conversation counts as expired. Claude Code also records usage data about these deadlines.\n\n**Why**\n\nA rewind can now be refused because of a deadline the server sets, not only because of the conversation's age.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}