{"version":"2.1.287","anchor":"remote-send-refusals-after-an-ambiguous-failed-post-are-no","canonical_anchor":"remote-send-refusals-after-an-ambiguous-failed-post-are-no","heading":"Remote messages are no longer reported as refused when they may have arrived","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/remote-send-refusals-after-an-ambiguous-failed-post-are-no","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Remote messages are no longer reported as refused when they may have arrived\n\nIf sending to a remote session failed unclearly and a retry is refused, Claude Code now reports the first error, not the refusal\n\n**What**\n\nWhen Claude Code sends something to a remote session and the attempt fails with a server error, a timeout or a network problem, it now remembers that failure. If a later retry is then refused, Claude Code reports the original failure instead of the refusal. The first attempt may have been saved by the server even though no reply came back.\n\n**Why**\n\nYou are no longer told a message failed outright when it may in fact have been delivered.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}