{"version":"2.1.248","anchor":"duplicate-and-retired-remote-permission-prompts-are-rejected","canonical_anchor":"duplicate-and-retired-remote-permission-prompts-are-rejected","heading":"Duplicate and retired remote permission prompts are rejected","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/duplicate-and-retired-remote-permission-prompts-are-rejected","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Duplicate and retired remote permission prompts are rejected\n\nRemote permission prompts no longer duplicate or come back after being retired.\n\n**What**\n\nOn a remote session, a permission request redelivered for an id that is already pending no longer produces a second prompt, and one that arrives after its id was retired locally is not revived.\n\n**Details**\n\n- An identical redelivery is skipped silently; a differing body keeps the prompt already shown and logs `remote_permission_request` with \"redelivered_mismatch\".\n- A request for a retired id is not re-armed and logs \"retired_id_rearmed\".\n- Removals now go through a retire path that records the id, and a turn ending with unresolved requests records their ids as retired as well as cancelling them, so late responses are recognised rather than treated as live.\n- Always on for remote sessions.\n\n**Evidence**\n\n`arrived again after it was retired here \u2014 not arming it`, `retirePermissionRequest(e) {`\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}