The request changes while it waits
Imagine a procurement request waiting for a manager. During that wait, the requester loses access to the account. Later, the original approval arrives. This is an illustrative scenario, not a customer incident.
The approval is only one input
An approval should bind to the material request, resource, revision and expiry. It does not override a later revocation or authorize a modified destination, amount or payload.
Resume the workflow, then recheck
A durable workflow can preserve the waiting state and resume when the approval arrives. Current identity and policy still need to be evaluated at the protected effect boundary.
Make the decision explainable
A denied effect should leave an attributable record of the applicable authority and reason. Preserve that evidence without storing raw credentials or unnecessary private data.