{"version":"2.1.304","anchor":"pending-state-writer-keeps-a-requeued-payload-separate-from","canonical_anchor":"pending-state-writer-keeps-a-requeued-payload-separate-from","heading":"Remote worker state updates no longer get merged into a retried update","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/pending-state-writer-keeps-a-requeued-payload-separate-from","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Remote worker state updates no longer get merged into a retried update\n\nA state update that is being resent is now kept apart from newer updates, and stops retrying once a newer worker status arrives\n\n**What**\n\nWhen Claude Code runs as a remote worker, it reports its state back over a connection. An update that failed to send and is queued to be sent again (a requeued update) is now held in its own separate slot. Before, there was a single waiting slot, and newer updates were merged into it on retry.\n\nNow:\n\n- Other waiting updates are no longer merged into the requeued one.\n\n- A requeued update that is still retrying stops when a new `worker_status` update arrives.\n\n**Why**\n\nThis fixes a bug where state reports from a remote worker could arrive in the wrong order, so the receiving side could see an older state after a newer one.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}