Help Index → When something does not behave as expected → Use case 56
A synchronization gate can block an operation, but it is not a guarantee that pending text will survive the next sync. Preserve every pending pane first: synchronizing one tab can refresh and overwrite the others.
Before you start
- Read the warning. Cancel unready write confirmations and keep NMS closed.
- Before any synchronization, Pretty Print or structured refresh, copy EACH pending Raw JSON pane to its own external file; syncing one tab can overwrite pending text in all others. Decide which edits are wanted before any sync or reload.
- A parse error can leave the old tree with a green light; [] is ignored, and Pretty Print can overwrite invalid pending text from the old model. Preserve text and verify actual values, not lights.
- Do not sync or Pretty Print Inventory Raw JSON: its current dictionary-assignment defect is not reliable inventory replacement. Use Organizer for supported moves or Replace Items from Backup for supported replacement.
Steps
- Inspect the Raw JSON synchronization status in all four processing tabs: bases, starships, inventories and teleport endpoints. A loaded-live indicator does not tell you that every editor matches the shared model. (control reference)
- Copy EACH pending editor to a separate external file before the first sync. Reapply wanted non-inventory edits from those copies one tab at a time, then sync and verify that tab before reapplying the next. Do not merely click Sync in each pending tab: earlier sync can overwrite later pending text. Do not sync/Pretty Print Inventory Raw JSON; use Organizer or supported replacement for those changes. (control reference)
- Wait for Processing to dismiss after each non-inventory sync, then compare the exact edited value in tree and text against its preserved copy. After a parse error, stop: the tree may still be old and the light green. [] is ignored; Pretty Print can overwrite invalid text with old model text. Correct and retry only understood edits, or preserve useful work and deliberately reload if abandoning them. (control reference)
- Retry the intended operation after resolving every pending tab. For File → Save, recheck the loaded slot and Main or Expedition context in the separate confirmation and accept only if all reviewed changes should be written. (control reference)
Expected result
- File → Save refuses unsynchronized text before requesting a live write. Organizer and guarded starship operations also require a synchronized source context.
- A cleared gate means the status checks passed, not that every intended edit survived. Verify all original pending edits against external copies before retrying the operation.
What changes, and when to save
Synchronization changes app memory only. Clearing this blocker is not a live-save completion; a separately confirmed File → Save and its verified result are still required. Never treat a cleared gate or green lights after a parse error or inventory sync as permission to save.
Check the result
- Confirm every tab’s intended edits survived and the retried action produced its expected result. A green synchronization light can coexist with unsaved modified data; that is not a contradiction.
Important details and recovery
- Do not synchronize unwanted text merely to clear a warning. Preserve other work and deliberately reload the disk save if you intend to abandon edits.
- Do not use legacy JSON export or Save As to bypass the live-save gate. They are not substitutes for writing the retained NMS target.
- Processing is noncancellable; do not repeatedly trigger sync while it is still running.