{"version":"2.1.286","anchor":"away-summary-cache-age-check-also-uses-a-second-timestamp","canonical_anchor":"away-summary-cache-age-check-also-uses-a-second-timestamp","heading":"Away summaries are skipped less often for a stale cache","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/away-summary-cache-age-check-also-uses-a-second-timestamp","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Away summaries are skipped less often for a stale cache\n\nThe summary shown when you return after being away now uses a second timestamp to judge cache age, so fewer are skipped\n\n**Unclear.** It is not known exactly what the second timestamp records.\n\n**What**\n\nWhen you come back to a session after being away, Claude Code can show a short summary of what happened. It skips the summary if the prompt cache, the saved copy of the conversation that makes requests cheaper, looks too old.\n\nThe age check now also takes a second timestamp into account and uses whichever is later. Fewer summaries are skipped for being \"cache stale\".\n\n**Why**\n\nIf the cache was renewed recently, you are more likely to see the summary.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}