{"version":"2.1.248","anchor":"transcripts-fall-back-to-a-second-store-when-the-primary-rea","canonical_anchor":"transcripts-fall-back-to-a-second-store-when-the-primary-rea","heading":"Transcripts fall back to a second store when the primary read fails","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/transcripts-fall-back-to-a-second-store-when-the-primary-rea","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Transcripts fall back to a second store when the primary read fails\n\nIf the main transcript store fails to read, a second store is tried instead of erroring.\n\n**What**\n\nLoading a saved transcript no longer fails outright if the primary storage read errors; it retries against a records-based store and reports which source served the data.\n\n**Details**\n\n- Size checks now prefer the stored byte count over the length of the buffer in memory.\n- The check for a truncated tail is skipped when the fallback path supplied the data.\n\n**Evidence**\n\n`loadTranscriptFile: v5 read failed (`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}