Skip to main content
Version: 1.x

SYNC331: Local record diverged

What this means​

This record on the device does not match your store and needs local repair.

Nothing you entered is waiting to be sent. The device's copy of a record your store owns has drifted from the store's copy; repair it according to the status shown in the log.

Your data​

No order or product data is affected. If this persists, export diagnostics and contact WCPOS support.

Troubleshoot​

  1. Expand the log entry - its context names the collection, the record id, the status and the detector that spotted the difference.
  2. For a changed or missing record, run a targeted download for the affected collection so the device replaces its copy with the store's.
  3. For a deleted record, remove the local copy; the server tombstone must not be downloaded.
  4. Compare the record in WP Admin with what the POS shows; a price or stock difference is the visible symptom.
  5. If the SAME records keep reappearing after repair, the store's stored digests are stale - this happens after a bulk write that skips WooCommerce's save hooks (a CSV import, a migration plugin, WP-CLI or direct SQL). The record itself is usually fine; WCPOS schedules a rebuild of the integrity index automatically once a range keeps reporting the same difference, and a site administrator can trigger it sooner.
  6. If it still returns after a rebuild, export debug info and contact support.

Details​

Code
SYNC331 (LOCAL_RECORD_DIVERGED)
Severity
warn
Introduced in
WCPOS 1.10.0