SYNC181: Local database call stalled
What this means
Saving or loading on this device is very slow, and its outcome is not yet known.
Nothing to do if WCPOS is working. If a screen stays stuck, reload WCPOS, then check your last change saved.
A single read or write to the local database on this device has gone unanswered for far longer than normal, while the database keeps answering everything else. This reporter only records the stall — it does not cancel or retry the operation, so the original call may still complete or fail later; the entry exists so a stuck screen or spinner leaves a trace naming exactly which operation stalled. Stalled sync work has a separate timeout and retry path — logged as a "Gave up on a stuck data request" entry under SYNC321. A stalled call from a screen stays pending until it finishes or the app is reloaded.
Your data
The result couldn't be confirmed — check before trying again. The stalled operation is usually a lookup, which changes nothing. If a change was being saved at that moment, open the record and confirm it saved — there may have been no visible symptom at all. The entry's context names the operation and the data collection involved.
Troubleshoot
- If WCPOS is working, there is nothing to do — the call most likely completed, just slowly. If the entry's operation was a save, open the record and confirm it saved.
- If a screen or spinner stays stuck, reload the app — on web, reload the browser tab; on desktop and mobile, close and reopen the app. That abandons the stuck operation; the screen loads again and asks the database fresh. A save that was in flight is not resent — open the record and confirm it saved.
- If this code returns regularly on the same device, use Copy debug info on the Logs tab and contact support — the entry's context names the operation and collection, the exact wait, and how busy the database was meanwhile.