{"version":"2.1.304","anchor":"worker-state-patches-that-get-a-4xx-are-requeued-when-they-c","canonical_anchor":"worker-state-patches-that-get-a-4xx-are-requeued-when-they-c","heading":"Remote session status is sent again when a larger update is rejected","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/worker-state-patches-that-get-a-4xx-are-requeued-when-they-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Remote session status is sent again when a larger update is rejected\n\nIf the server rejects a remote session's status update that carried other information too, Claude Code now resends the status part instead of dropping it\n\n**What**\n\nIn a remote session, Claude Code sends updates about the session's state to the service. When the service rejected one of these updates as a bad request, Claude Code used to log it and drop the whole update.\n\nNow, if the rejected update carried other information besides the session's status, Claude Code queues just the status part, together with a note on whether replies are degraded, to be sent again.\n\n**Why**\n\nThe session's status is less likely to be lost because another part of the same update was rejected.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}