{"version":"2.1.248","anchor":"transcripts-load-even-when-the-storage-backend-refuses-range","canonical_anchor":"transcripts-load-even-when-the-storage-backend-refuses-range","heading":"Transcripts load even when the storage backend refuses ranged reads","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/transcripts-load-even-when-the-storage-backend-refuses-range","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Transcripts load even when the storage backend refuses ranged reads\n\nTranscripts still load when your storage backend refuses ranged reads.\n\n**What**\n\nIf the very first partial read of a stored transcript fails with a recognisable error, Claude Code now streams the whole object through the same parser instead of giving up with \"transcript ranged read failed\".\n\n**Details**\n\n- The fallback applies only to a failure at offset 0; later chunk failures still surface as errors.\n\n**Evidence**\n\n`transcript ranged read failed`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}