Sync Center

Tab Sync. This is the technician control room for the outbox. Title: Sync. Route /app/sync. A green list here is not the same as a Firebase notification.

Screen path: bottom bar Sync. Native Field is not the Field PWA.

Healthy Sync Center (Up to date / Attention 0). Sample data. This screenshot is not a Needs Attention state.

Preconditions

A Field session. Sync now needs the radio (except to show cached status). FIELD-009 is this healthy screen — this documentation does not invent a conflict UI screenshot.

Loop

1. Read Status and Last synced.
2. Tap Sync now to run the same engine as bringing the app to the foreground.
3. Filter: Attention, Pending, or All. Empty: Nothing waiting to sync.
4. If work is still queued, tap Retry pending.
5. Failed photos: Failed uploads. Copy Diagnostics from the app bar if you escalate.

UI	Meaning
Up to date	Nothing waiting in the outbox
Needs attention	Conflict, rejection, or a failed upload
Offline — work is saved on this device	Radio down; keep working
Syncing…	A run is in progress
Sign in again to continue sync	Session expired (typically 401)
This app is not compatible with the server	Protocol mismatch — update both
Sync now	Push then pull while the app is running
Retry pending	Retry queued ops (same id)

Chips can show Attention N and Pending N. Attention 0 means healthy — never describe that screenshot as Needs Attention.

Categories: Job, Forms, Photos, Signatures, Parts. Badges: Saved on this device, Waiting to sync, Needs attention, Waiting on another item.

What works / does not work

	Works	Does not work
Foreground / Sync now	Yes	Periodic sync while killed
Synced on a photo	File uploaded and accepted	“HTTP 200 on an unrelated call”
Complete job confirmed	After pull shows Completed	While a completion row is still pending

App bar Diagnostics copies support-safe text. Do not paste tokens.

If Success did not clear every row: a photo may still be uploading or a conflict remains. Read the row. Do not repeat the original business action yet.