Approving a held message from another session re-checks policy, so a revoked one stays blocked.
What's wrong with this entry?
Approval 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.
held peer message approved but policy is now refuse
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.