Review the schema findings in context

Treat a finding as a prompt to inspect the active schema branch, its declared draft, and the intended contract—not as an automatic correction.

Investigate references and structural drift

  1. Open the schema and the referenced resources needed for a reproducible case.
  2. Review unresolved local or external $ref findings by checking the target resource and JSON Pointer.
  3. Check structural findings such as an unknown keyword, an incompatible type, or a property that remains in required after its definition changed.
  4. Compare the finding with version-control history before restoring, removing, or revising the rule.

The Help lists many individual analyzer messages, including reference, keyword, type, range, and required-property checks. Their exact coverage and classification are product-specific.

Correct deliberately and retest data

Follow a result to the reported schema location, make one intentional correction, and run the current schema analysis again. Then validate one JSON instance expected to pass and one expected to fail. This separates a quiet analyzer result from proof that the data contract still behaves as intended.

Related schema tasks

JSON Schema editorJSON Schema debuggerJSON Schema analyzer overview