{"version":"2.1.247","anchor":"device-hooks-consent-gains-a-distrusted-outcome-when-the-sav","canonical_anchor":"device-hooks-consent-gains-a-distrusted-outcome-when-the-sav","heading":"Device-hooks consent gains a distrusted outcome when the saved answer's file cannot be checked","tier":"notice","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/device-hooks-consent-gains-a-distrusted-outcome-when-the-sav","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Device-hooks consent gains a distrusted outcome when the saved answer's file cannot be checked\n\nIf your saved hooks-sharing answer can't be verified, you're asked to decide again in \/hooks.\n\n**What**\n\nWhen a cloud session is offered this machine's hooks, a stored answer is ignored if the session could write the file holding it. That check can now fail outright, producing a new result telling you the file could not be located to check who can write it and asking you to decide in `\/hooks`.\n\n**Details**\n\n- Only applies on the cloud-session hooks path.\n- The switched-off message is now the actual reason truncated to 200 characters; the previous fixed text about device binding likely being off was removed.\n- Registration outcomes `consent_distrusted`, `dormant` and `failed` are now reported separately in telemetry.\n- Answering \"not now\" now clears the session's pins and standing rather than only disarming.\n\n**Evidence**\n\n`could not be located to check who can write it. Decide for this session in \/hooks.`, `consent_distrusted`\n\n- Area: Cloud Sessions\n- Names: `\/hooks`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}