Consistency check

endAge smaller than startAge, or not an integer

Symptom

With decimals a schema error 'must be integer'; with swapped bounds the schema accepts and the receiver rejects.

Cause

Since Release 2026 age bounds are integers; the unit (years or months) is a chain agreement and confusion about it leads to reversed bounds.

Fix

Check startAge ≤ endAge and keep one unit in all messages.

{ "startAge": 34, "endAge": 25 }

{ "startAge": 25, "endAge": 34 }

Check your own message for this and all other errors with the free validator: schema, code lists and consistency checks in one report.Validate a message