Group of 2 Nothing to try yet
A new failOpenVerdict signal lets certain org-policy checks proceed when the compliance verdict service is unreachable
What
Org-policy compliance checks now have a fail-open path for when the system that decides compliance verdicts is unreachable:
- A new
failOpenVerdictboolean is tracked in the session's policy-limits cache and updated wheneverreplaceSessionCacheor hint updates run. - The cache also emits a new
heldStartSignalon everyemitVerdictChanged()call, separate from the verdict-changed signal itself. - When the verdict service is unreachable and the identity that settled without a verdict matches the current principal, certain otherwise-denied compliance keys (such as HIPAA-related ones) become allowed again, unless the required HIPAA evidence hasn't been loaded or can't be read.
Why
This prevents a temporarily unreachable compliance-verdict service from blocking users outright, while still requiring the right evidence to be present before allowing HIPAA-related actions through the fail-open path.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
Which specific compliance keys or actions this exception applies to is not stated