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.

What to do​

Restart WCPOS; if this keeps happening the local data on this device needs repair. WCPOS does not retry this by itself — retry when you are ready.

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; a site administrator can clear it by rebuilding the integrity index, and WCPOS schedules that rebuild automatically once a range keeps reporting the same difference.
  6. If it still returns after a rebuild, export debug info and contact support.

Where to look​

When WCPOS can save this error, it is recorded on the device that raised it. Open Store health → Logs (the heart-pulse icon at the bottom of the navigation drawer), find the entry marked with this code and expand it: the expanded row shows the plain-language reason and the context captured at the moment of failure. For a store request, that context may include the server’s own error code (serverCode), the HTTP status or the endpoint; the fields shown depend on where the failure occurred. When reporting a problem, use Copy debug info at the top of the Logs screen (Share debug info on phones and tablets) rather than screenshots: it bundles the app version, connection state and the most recent errors. Logs are kept for at most 30 days, so collect them while the problem is fresh. Also copy any browser-console error that appeared before the POS was able to write its own log entry.

Details​

  • Code: SYNC331 (LOCAL_RECORD_DIVERGED)
  • Severity: warn
  • Introduced in: WCPOS 1.10.0