{"version":"2.1.227","anchor":"approving-a-held-peer-message-re-checks-policy-first","canonical_anchor":"approving-a-held-peer-message-re-checks-policy-first","heading":"Approving a held peer message re-checks policy first","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/approving-a-held-peer-message-re-checks-policy-first","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Approving a held peer message re-checks policy first\n\nApproving a held message from another session re-checks policy, so a revoked one stays blocked.\n\n**What**\n\nApproval of a message held from another session now re-evaluates the inbound policy at the moment you approve. If it has since flipped to refuse, through the kill switch or an opt-out, the message is dropped with an expired or denied receipt instead of being released into the queue.\n\n**Evidence**\n\n`held peer message approved but policy is now refuse`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}