{"version":"2.1.221","anchor":"cleared-sessions-from-the-v5-store-no-longer-stat-the-filesy","canonical_anchor":"cleared-sessions-from-the-v5-store-no-longer-stat-the-filesy","heading":"Cleared sessions from the v5 store no longer stat the filesystem for a timestamp","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/cleared-sessions-from-the-v5-store-no-longer-stat-the-filesy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Cleared sessions from the v5 store no longer stat the filesystem for a timestamp\n\nCleared sessions get their date from what was already read instead of touching the disk.\n\n**What**\n\nWhen a transcript resolves to no usable leaf and the session was cleared to empty, the loader takes the timestamp from the read result instead of calling `stat()` on the session file.\n\n**Details**\n\n- sessions loaded via the storageV5 backend carry `v5Read: { mtimeMs }` forward, and that mtime is used for the entry's date, created and modified\n- when the mtime is absent the current time is used\n- this matters where a v5 key has no real file on disk to stat\n\n**Evidence**\n\n`v5Read: { mtimeMs: i.mtimeMs },`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}