{"version":"2.1.284","anchor":"sessions-v2-event-posts-detect-payloads-that-are-too-large","canonical_anchor":"sessions-v2-event-posts-detect-payloads-that-are-too-large","heading":"Remote sessions can recognise events that are too large to send","tier":"internal","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/sessions-v2-event-posts-detect-payloads-that-are-too-large","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Remote sessions can recognise events that are too large to send\n\nSending session events now reports when the service rejected them as too large, instead of treating it as a general failure\n\n**Unclear.** What remote sessions do after an event is flagged as too large, and whether it is retried, is not clear.\n\n**What**\n\nWhen Claude Code sends session events to Anthropic's session service, it now flags a rejection as too large in two cases. One is a 413 error. The other is a 400 error whose message shows the size was the problem. Before, a 400 was treated as a general error.\n\n**Why**\n\nRemote sessions can handle oversized events on their own terms instead of treating them as a general failure.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}