Offline sync stuck or not completing

The Servinix Go app came back online but the sync indicator keeps spinning, or actions taken while offline never reach the server.

Why this happens

The device shows a network connection but the Servinix API is temporarily unreachable, so the queue cannot drain.
A queued request has a malformed payload (for example, a job action taken after the session token expired). The queue retries it repeatedly, blocking later items.
Battery optimisation on Android is suspending the background sync service.
Push notifications are disabled, so the app is not woken to process the queue on reconnection.

Open a browser on the device and load any page to confirm the connection is genuinely active — some mobile networks show connected but block API traffic.
Force-close the Servinix Go app (swipe it away from the app switcher), then reopen it. The native sync queue restarts on launch and retries all pending requests.
On Android, go to Device Settings → Apps → Servinix Go → Battery and set the battery option to Unrestricted. Aggressive battery modes can suspend the background sync service.
In the app, go to Me → Notifications and confirm push notifications are enabled. Push wakeups help the queue drain after reconnection.
If the queue count does not decrease after several minutes online, sign out and sign back in. The app re-fetches current server state on login.

If a malformed request is blocking the queue, signing out is the fastest way to clear it. Re-apply any job actions after logging back in.
If failures continue across multiple sessions, contact Servinix support with: device model, OS version, approximate time the issue started, and which actions were taken offline.
Use Me → Submit a bug report to attach an app log bundle — this captures the sync queue state at the time of the report.