{"version":"2.1.304","anchor":"remote-session-sends-409-triggers-a-recovery-call-and-boots","canonical_anchor":"remote-session-sends-409-triggers-a-recovery-call-and-boots","heading":"Remote sessions try to recover when a message send hits a conflict","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/remote-session-sends-409-triggers-a-recovery-call-and-boots","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Remote sessions try to recover when a message send hits a conflict\n\nWhen sending to a remote session fails with a conflict error, Claude Code now runs a recovery step instead of giving up\n\n**What**\n\nWhen Claude Code sends a message to a remote session and the server answers with a conflict error (status 409), it used to show a warning and give up. It now runs an extra recovery step.\n\nWhen attaching to an existing remote session, messages queued while the connection is being set up are now marked to wake that session.\n\n**Why**\n\nThis should make remote sessions recover more often from a failed send.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}