# SYNC181: Local database call stalled

## What this means[​](#what-this-means "What this meansへの直接リンク")

A local database operation is taking far longer than normal; its outcome is not yet known.

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](/ja/error-codes/SYNC321.md). A stalled call from a screen stays pending until it finishes or the app is reloaded.

## Your data[​](#your-data "Your dataへの直接リンク")

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[​](#troubleshoot "Troubleshootへの直接リンク")

1. If everything is working, no action is needed — the call most likely completed, just slowly.
2. 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.
3. If this code returns regularly on the same device, export debug info from the Logs screen and contact support — the entry's context names the operation and collection, the exact wait, and how busy the database was meanwhile.

## Details[​](#details "Detailsへの直接リンク")

* Code

  `SYNC181` (`LOCAL_DB_STALLED`)

* Severity

  warn

* Introduced in

  WCPOS

  <!-- -->

  1.10.6