{"version":"2.1.280","anchor":"cloud-code-review-failure-guidance-now-varies-by-failure-rea","canonical_anchor":"cloud-code-review-failure-guidance-now-varies-by-failure-rea","heading":"Cloud code-review failure guidance now varies by reason","tier":"notice","area":"Code Review","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/cloud-code-review-failure-guidance-now-varies-by-failure-rea","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Cloud code-review failure guidance now varies by reason\n\nFailed cloud \/code-review runs now show tailored guidance based on why they failed instead of one generic message\n\n**What**\n\n- The failure message shown when a cloud `\/code-review` run fails no longer always tells the user to retry `\/code-review ultra` or fall back to local review. It now branches on the specific failure reason, such as `session_archived`, `stopped_remotely`, or `session_not_found`, only recommending the ultra\/local retry for a subset of causes.\n\n- Whether a poll that repeatedly gets 404s is treated as `session_not_found` versus just a timeout is now controlled by a remote-config flag, `tengu_breezy_diffie`.\n\n**Why**\n\nThis gives clearer, more accurate next steps when a cloud code review fails, instead of always pointing to the same generic retry advice regardless of the actual cause.\n\n- Area: Code Review\n- Names: `\/code-review ultra`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}