Syncing with the mobile app

The mobile app stores reports locally and syncs them with the cloud once a connection and a valid sign-in are available. That applies to Solo and Cloud. The Offline product does not sync: Offline license.

Offline work and on-device backup: Working offline. The three paths: Solo, Offline, and Cloud.

When sync runs

• Automatically on an interval under Settings → Cloud sync (default 15 minutes; also 5 / 30 / 60 minutes, or Off)
• If Wi‑Fi only is on (the default), automatic syncs do not use cellular. Manual sync always remains available
• After the network returns, once the chosen connection is back
• When returning to the app, if the interval has elapsed since the last sync
• On app launch, if there are pending local changes
• Manually: the Sync now button, or the sync icon at the top right
• When leaving the mapping canvas (push of the open drawing, without a full pull)
• Optionally Force full sync — reloads all server data; local changes are uploaded first

Automatic sync pauses while you are drawing on the mapping canvas. Without a sign-in or without a matching connection, data stays on the device. The Offline product does not sync.

What is synced

Both directions (device → cloud and cloud → device), including:

• Artworks and condition reports
• Mapping (layers, strokes, damage markers)
• Views and images (images are uploaded and downloaded separately)
• Form definitions and bound form values

Finalized reports are read-only. Sync does not change them — pending local edits to those reports are skipped.

After sign-out, local data remains on the iPad and is available again at the next login.

Sync conflicts

A conflict occurs when the same record was changed at the same time on the tablet and on another device (Admin or a second iPad).

Canvas conflict (mapping)

The mapping is compared as a complete stand — not stroke by stroke. While the conflict is open, the tablet does not push that mapping again.

In the web app the report shows a notice with Resolve conflicts:

The iPad report view also shows a warning banner; visual resolution (preview and merge) lives in the web app under Sync → Conflicts.

There you see tablet and server stands side by side, including layer, stroke, and annotation counts:

Three paths:

Action	Result
Accept tablet	Only the tablet stand remains. Anything that exists only on the server is removed.
Keep server	The server stand stays. Tablet mapping changes are lost.
Merge	Content from both sides is combined. New strokes are added automatically; places with the same ID but different content you choose one by one.

If the two mappings share no common layer IDs, merge stacks both versions — the result then matches neither preview.

After resolution, the next sync brings the chosen stand onto the tablet.

Field conflicts (metadata)

Simultaneous edits to fields such as title, notes, or inventory number are tracked as a field conflict (artwork or condition report). Resolve them:

• in the web app under Sync → Conflicts (accept client / keep server)
• or on the iPad under Settings, when open conflicts are listed there

Typical flow

1. Work on the iPad — including offline
2. Sync (automatic interval, launch, or Settings)
3. On a canvas conflict: compare in the web app and pick one of the three strategies
4. Sync again so the tablet picks up the resolved stand

See also: Working offline, Supported devices.