> ## Documentation Index
> Fetch the complete documentation index at: https://helpdocs.servinix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Offline mode and sync

> How the Servinix Go app queues requests when offline and syncs automatically when connectivity is restored so technicians never lose field data.

# Offline mode and sync

Servinix Go keeps working when your phone loses connectivity. The app queues changes locally and uploads them automatically as soon as the connection returns — no manual sync step required.

## How offline mode works

All API requests that record field activity are marked as persistable. When the app detects no network, these requests are stored in a local queue on the device. The native layer manages the queue outside the app's main thread, so queued items survive the app being backgrounded.

When connectivity is restored, the app drains the queue in order, uploading each item to the Servinix API. A system notification confirms when the upload is complete (for example: "12 pending updates were uploaded when connection returned").

The connection status is visible on the **Me** tab under **App Info**: the **Connection** row shows **Online** in green or **Offline** in red.

## What works offline

The following actions can be completed without an active connection:

* Viewing schedule and job details already loaded on the device
* Progressing through job statuses (travel start, I'm Here, start work, complete)
* Completing tasks and adding notes
* Capturing photos (stored locally until upload)
* Collecting a customer signature
* Logging time entries

## What requires connectivity

* Loading jobs or schedule data not yet fetched from the server
* Sending a payment link or processing a card payment
* Sending an estimate to a customer
* Receiving new dispatch notifications

## How sync works

The app syncs automatically — there is no manual "sync now" button.

1. An action is taken in the app (for example, completing a task).
2. If online, the request is sent immediately and the server confirms.
3. If offline, the request is stored in the local queue.
4. When the network returns, queued requests upload in the background.
5. A system notification appears in the Notification Center when the queue drains.

## Result / verify

After reconnecting, the **Connection** row on the Me tab shows **Online**. Job statuses, task completions, and photos are reflected in the portal once the queue clears.

## Troubleshooting

If the queue is not clearing after reconnecting, see [Offline sync stuck or not completing](/field-service-management/fsm-troubleshooting/offline-sync-stuck) for diagnostic steps.

## Related

* [Tech mobile app overview](/field-service-management/tech-mobile-app/tech-mobile-app-overview)
* [Offline sync stuck or not completing](/field-service-management/fsm-troubleshooting/offline-sync-stuck)
* [Job lifecycle](/field-service-management/jobs-and-work-orders/job-lifecycle)
* [Capture customer signature](/field-service-management/jobs-and-work-orders/capture-customer-signature)