{"version":"2.1.223","anchor":"session-resume-falls-back-to-scanning-transcripts-by-id","canonical_anchor":"session-resume-falls-back-to-scanning-transcripts-by-id","heading":"Session resume falls back to scanning transcripts by id","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/session-resume-falls-back-to-scanning-transcripts-by-id","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Session resume falls back to scanning transcripts by id\n\nResuming a session by its id now works even when the usual lookup misses it.\n\n**What**\n\nResuming a session by string id no longer fails when the usual lookup misses it.\n\n**Details**\n\n- An additional lookup path scans transcripts for the id.\n- When the scan is what found the session, `tengu_transcript_id_scan_fallback` is recorded.\n\n**Evidence**\n\n`tengu_transcript_id_scan_fallback`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}