E1703. Approval policy version conflict

Severity: ERROR. Class: HITLPolicyVersionConflictError (subclass of HybridModeError).

What happened

The approver opened the approve-forever diff modal against policy version N; another admin published version N+1 before the approver clicked Confirm. The backend rejects the stale diff.

Why it matters

Approve-forever inserts a rule into a specific policy version. If the version moved under the modal, applying the diff would corrupt the new version's intent.

How to fix

The approver UI auto-refreshes the diff against the new version; the approver re-confirms against the current state. No action required from the SDK side; the rejected approval surfaces as a normal deny.

Catching this error

except HybridModeError catches this. Hybrid-mode customers see this most often during high policy-edit traffic.

See also

• Approval Workflow. The parent concept
• SDK: Approval callback. The request_approval + wait API
• Errors index