Distinguish valid JSON from a known state
JSON permits strings; it does not define your application’s status meanings. This local contract recognises queued, complete and cancelled. A new string remains unknown until the integration owner updates the mapping. Do not map every unrecognised value to success.
| Raw status | Local interpretation | Allowed action |
|---|---|---|
| queued | Pending | Monitor under status budget |
| complete | Completion confirmed by this contract | Apply agreed follow-up once |
| paused-by-review | Unknown | Hold irreversible actions and inspect contract |
Update the mapping with an acceptance case
Keep raw data and the contract version for investigation, with sensitive fields excluded. A revised mapping needs a named owner and a test showing which actions are permitted. Reprocess held records deliberately rather than losing them during a parser update.
A provider adds “reviewed”, but your mapping knows only “complete”. Can you treat the words as equivalent?
Show the worked answer
No. Obtain the documented meaning and business decision first. Keep reviewed as an unknown raw value until the new rule and tests are approved.