{"version":"2.1.228","anchor":"sessions-no-longer-fall-back-to-a-made-up-transcript-path","canonical_anchor":"sessions-no-longer-fall-back-to-a-made-up-transcript-path","heading":"Sessions no longer fall back to a made-up transcript path","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/sessions-no-longer-fall-back-to-a-made-up-transcript-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Sessions no longer fall back to a made-up transcript path\n\nResuming a session no longer points at a transcript file that was never there.\n\n**What**\n\nWorking out which transcript file belongs to a session id now reports one of three answers: found, definitely absent, or present but unverifiable. An unverifiable candidate is remembered and used as a last resort instead of the code inventing a path that does not exist.\n\n**Details**\n\n- Listing calls to the storage backend are memoized during a single resolution, so repeated transcript listings do not re-page the backend.\n\n**Evidence**\n\n`unverifiable`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}