DEBUGGING PLAYBOOK · REVIEWED 2026-10-08

An order ID changes after parsing

A large numeric identifier can lose its last digit when a consumer parses it. Inspect the original response before passing it to another converter.

Sample input

{"orderId":9007199254740993,"paid":false}

Steps and checks

  1. Load the diagnostic sample and press Format.
  2. The output must still contain 9007199254740993. A precision warning is expected; Locate selects the source number.
  3. Check the producer’s contract. If this is an opaque identifier, request a string from the producer; do not guess digits after parsing.

Reference result

{
  "orderId": 9007199254740993,
  "paid": false
}

Avoid a misleading conclusion

Formatting can succeed while a precision warning remains. This formatter preserves number tokens; many consumers do not. Syntax errors must be fixed separately.

What to do next

After the producer supplies the correct string ID, validate its structure against the actual Schema. Keep original response bytes for signature verification.

Related case and technical reference · Report an error or missing edge case

Continue this workflow

Why a duplicate JSON key can change an order status →

Keep a large order ID intact when processing JSON →

About this tool

Check JSON syntax and locate errors while formatting without rewriting number tokens or removing duplicate keys. Detect duplicate fields and JavaScript numeric precision risks.

How to use

Paste JSON and select Format. Use Locate to select an issue, then pass the original input to YAML conversion or JSON comparison.

Tips & Notes

Input is limited to 1,000,000 characters and 128 levels of nesting. This is not schema validation. Formatting changes whitespace; use original bytes for signature verification.