{"version":"2.1.260","anchor":"unattended-serving-consent-now-also-blocked-by-stale-unreso","canonical_anchor":"unattended-serving-consent-now-also-blocked-by-stale-unreso","heading":"Unattended-serving consent now also blocked by 'stale unresolved' state","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/unattended-serving-consent-now-also-blocked-by-stale-unreso","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Unattended-serving consent now also blocked by 'stale unresolved' state\n\nUnattended cloud commands now also treat stale unresolved consent as not consented.\n\nThe check for whether a cloud-triggered unattended command is consented-to on this machine now also treats a \"stale unresolved\" consent record as unconsented, in addition to the existing checks for managed decline, missing acceptance, and revocation.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}