SYNC321: Sync partial
What this means
Some data didn't sync this time.
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. Nothing to do if the next sync clears it. If Store health → Database lists changes that need attention, settle them there.
- "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
Don't clear this device's data — it may hold changes your store doesn't have yet. For a gave-up data request, nothing was changed — an abandoned request is re-issued automatically. If this keeps happening, use Copy debug info on the Logs tab and contact WCPOS support.
Troubleshoot
- For a "Gave up on a stuck data request" entry, no action is needed unless a screen stays stuck. Then reload the app — reload the browser tab on web, or close and reopen the app on desktop and mobile.
- For a partial sync, nothing to do if the next sync clears it. If it doesn't, open Store health → Database: records that still did not sync appear at the top. The "… records need attention" callout names the first one with its reason (fix it and the next one appears), and the "… changes never reached your server" and "… changes were held" panels list theirs. The records that did sync need nothing.
- Settle each listed record by its own reason. In the callout, Fix record (where shown) opens the record to edit it; a refused change is corrected on the record itself (SYNC201); for a held change, choose which version to keep (SYNC221).
- Then send them again: Retry in the callout (this runs a sync), or Send again on the record's row in the panels. A record the callout says can't download from your store has no Retry — see SYNC331.
- If a record still does not sync, use Copy debug info on the Logs tab and contact support.