Skip to main content
Version: 1.x

SYNC321: Sync partial

What this means

Some records synced, but one or more records did not.

This code appears in two forms — the log row's title says which one you have:

  • "Sync partial" (record titles): some records synced and the named records did not. Review each named record and its reason before retrying only those records.
  • "Gave up on a stuck data request": the sync engine's data-request lane stopped making progress on one request, so after a generous wait the app abandoned that request rather than let it block everything queued behind it. Nothing needs retrying by hand — the sync engine re-issues the request automatically — and it often follows a stalled local database call, logged separately as SYNC181.

Your data

For records that did not sync: the change is saved on this device but has not reached your store. If this persists, export diagnostics and contact WCPOS support. For a gave-up data request: nothing was changed — an abandoned request is re-issued automatically.

Troubleshoot

  1. For a partial sync: expand the log entry to list which records did not sync and the reason each one gives.
  2. Handle each named record by its own reason — an invalid field needs editing, a conflict needs comparing with the store.
  3. Retry only the records that failed; the rest are already synced and need nothing.
  4. For a "Gave up on a stuck data request" entry, no action is needed unless the screen stays stuck — then reload the app, and if it keeps happening, export debug info and contact support.

Details

Code
SYNC321 (SYNC_PARTIAL)
Severity
warn
Introduced in
WCPOS 1.10.0