{"version":"2.1.309","anchor":"worker-state-4xx-drop-requeues-metadata-differently","canonical_anchor":"worker-state-4xx-drop-requeues-metadata-differently","heading":"Rejected remote session updates keep their details for resending","tier":"internal","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/worker-state-4xx-drop-requeues-metadata-differently","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Rejected remote session updates keep their details for resending\n\nWhen a remote session status update is rejected, its details are now put back in the queue to be sent again\n\n**What**\n\nA remote worker sends status updates about its session. When the server rejects one with a client error, Claude Code now puts the update's details back in the queue to be sent again, in more cases than before.\n\n**Why**\n\nFewer of these updates should be lost.\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}