{"version":"2.1.224","anchor":"sharing-a-transcript-retries-with-smaller-payloads-instead-o","canonical_anchor":"sharing-a-transcript-retries-with-smaller-payloads-instead-o","heading":"Sharing a transcript retries with smaller payloads instead of failing","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/sharing-a-transcript-retries-with-smaller-payloads-instead-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Sharing a transcript retries with smaller payloads instead of failing\n\nSharing an oversized transcript now retries with trimmed versions instead of just failing.\n\n**What**\n\nWhen a transcript is too large to share, Claude Code now tries progressively stripped versions rather than giving up. It walks a ladder of candidates (full, without the last API request, raw transcript lines only, metadata only), size-checks each before sending, and posts the first that fits.\n\n**Details**\n\n- A successful reduced upload records \"payload_stripped\" so it's visible that content was trimmed.\n- Size failures and `RangeError` during serialisation fall through to the next variant; the precheck reports `payload_too_large_precheck`.\n- Blocked outcomes (essential-traffic-only mode, data residency, auth) still fail immediately with their own reason codes and are not retried.\n\n**Evidence**\n\n`payload_too_large_precheck`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}