{"version":"2.1.242","anchor":"attaching-to-a-cloud-session-fails-fast-on-a-bad-session-id","canonical_anchor":"attaching-to-a-cloud-session-fails-fast-on-a-bad-session-id","heading":"Attaching to a cloud session fails fast on a bad session id","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/attaching-to-a-cloud-session-fails-fast-on-a-bad-session-id","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Attaching to a cloud session fails fast on a bad session id\n\nAttaching to a cloud session with an unknown or malformed id is refused immediately with a message.\n\n**What**\n\nAttaching to a remote session used to log a failed lookup and carry on over the websocket anyway. An unknown session id or a malformed one is now refused outright with a message saying so; other lookup errors still fall through to the websocket as before.\n\n**Details**\n\n- The refusal records a `tengu_remote_attach_session_rejected` event carrying the reason.\n\n**Evidence**\n\n`cloud attach refused: the id names no session of this account, or is malformed`\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}