{"version":"2.1.314","anchor":"cloud-branch-missing-error-reworded","canonical_anchor":"cloud-branch-missing-error-reworded","heading":"Missing-branch error for cloud sessions gives clearer next steps","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/cloud-branch-missing-error-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Missing-branch error for cloud sessions gives clearer next steps\n\nWhen a cloud session's branch is missing on the remote, the error now says to push it or restore it, then send a message or start anew\n\n**What**\n\nWhen a cloud session's git branch cannot be found in the remote repository, the error now says to push the branch if it was never pushed, or restore it from its pull request. Then send a new message or start a new session. The old message assumed the branch was deleted after a merge and told you to click Try again.\n\n**Why**\n\nThe message now also covers branches that were never pushed, not just ones deleted after merging.\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"}