Skip to content
VB-OSVB-OSVB-OS Docs

Troubleshoot DEFER Verdicts in VB-OS

A DEFER verdict means the evaluation did not pass. The failure_reasons in the response tell you exactly why.

Stage 1: Admissibility (admissibility_not_satisfied)

Section titled “Stage 1: Admissibility (admissibility_not_satisfied)”

Missing required evidence:

The workload is missing a field declared with require_evidence. Check that all required fields are present and non-null.

Type mismatch:

A field declared with require_type has the wrong type. For example, require_type: amount: integer fails if amount is a string.

Conditional evidence not met:

A require_evidence IF condition evaluated to true, but the conditional field is missing.

Stage 2: Prohibition (prohibited_evidence_present)

Section titled “Stage 2: Prohibition (prohibited_evidence_present)”

Prohibited evidence present:

The workload contains a field declared with prohibit_evidence. Remove the prohibited field from the workload.

Conditional prohibition triggered:

A prohibit_evidence WHERE condition evaluated to true. The field is present and its value matches the prohibition condition.

Additional failure types:

  • conditional_evidence_missing: a require_evidence IF condition evaluated to true, but the conditional field is missing
  • conditional_prohibition_violated: a prohibit_evidence WHERE condition was triggered

Stage 3: Predicate Failure (predicate_failed)

Section titled “Stage 3: Predicate Failure (predicate_failed)”

Predicate conditions not met:

One or more predicates evaluated to false. The failure_reasons list each failing predicate with its name and the expression that failed.

All failing predicates are reported, not just the first one, giving complete visibility into what needs to change.

Debugging Steps

Section titled “Debugging Steps”
  1. Read the failure_reasons array in the evaluation response
  2. Identify the failure type (admissibility_not_satisfied, prohibited_evidence_present, predicate_failed, conditional_evidence_missing, or conditional_prohibition_violated)
  3. Compare the workload fields against the boundary requirements
  4. For predicate failures, verify the field values satisfy the comparison

Next Steps

Section titled “Next Steps”