{"version":"2.1.224","anchor":"repl-bridge-failures-record-whether-they-were-an-auth-proble","canonical_anchor":"repl-bridge-failures-record-whether-they-were-an-auth-proble","heading":"REPL bridge failures record whether they were an auth problem","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/repl-bridge-failures-record-whether-they-were-an-auth-proble","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### REPL bridge failures record whether they were an auth problem\n\nBridge failures are now labelled as authentication or terminal, though nothing reads the label yet.\n\n**What**\n\nBridge failures are now tagged as either an authentication problem or a terminal one, alongside the existing error. Missing OAuth token, missing organization and unenrolled trusted device count as auth; everything else defaults to terminal. Nothing user-visible changes yet.\n\n**Evidence**\n\n`replBridgeErrorKind`\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}