{"version":"2.1.288","anchor":"failed-first-cloud-message-now-explains-why","canonical_anchor":"failed-first-cloud-message-now-explains-why","heading":"A first cloud message that may not have arrived now says why","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/failed-first-cloud-message-now-explains-why","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### A first cloud message that may not have arrived now says why\n\nThe warning for a first cloud-session message that may not have arrived now gives a plain reason, such as the service being busy\n\n**What**\n\nWhen you send the first message to a cloud session and Claude Code cannot confirm it arrived, the warning now gives the reason in plain words. Examples:\n\n- the service is busy\n\n- the service took too long to answer\n\n- the connection failed\n\nBefore, the warning showed a raw internal reason.\n\n**Why**\n\nYou can tell from the warning what went wrong, which makes it easier to decide whether to wait and try again.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}