{"version":"2.1.239","anchor":"reworded-auth-doctor-and-artifact-messages","canonical_anchor":"reworded-auth-doctor-and-artifact-messages","heading":"Reworded auth, doctor and artifact messages","tier":"notice","area":"Auth","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/reworded-auth-doctor-and-artifact-messages","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Reworded auth, doctor and artifact messages\n\nAuth, \/doctor and artifact messages now describe what actually happened instead of guessing a fix.\n\n**What**\n\nSeveral messages were rewritten to describe what actually happened. A device-proof failure now says there is \"no trusted-device token here, and this machine could not be enrolled for one\" instead of suggesting `\/login`, and `\/doctor` shows \"Remote Control availability could not be verified\".\n\n**Details**\n\n- The `\/doctor` Remote Control rows no longer use the word \"rollout\".\n- Both reasons given when live artifact updates are unavailable now say you will not be notified here when this artifact is republished elsewhere, rather than referring to other sessions' republishes.\n\n**Evidence**\n\n`Remote Control availability could not be verified`\n\n- Area: Auth\n- Names: `\/doctor`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}