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

# The Sync Center

> Resolving collisions, reading failed operations, and managing the handsets in your plant.

The main app's view of the handsets. Reached from the sync icon in the header, beside the
notification bell — nobody opens a navigation item to find out whether something is stuck.

<img src="https://mintcdn.com/assetinfinity/95UxrhuglB-erOSy/images/field/sync-center.png?fit=max&auto=format&n=95UxrhuglB-erOSy&q=85&s=0357d5c448ccf43bb866136689167776" alt="The Sync Center" width="2880" height="1800" data-path="images/field/sync-center.png" />

## Three questions, in order

### 1. What needs a decision?

**Collisions**, first and largest, because they are the only thing here that will not resolve
itself.

A pending operation goes when there is signal. A failed one may go on the next attempt. A collision
waits for a person **indefinitely** — so filing it under a device inventory would be letting it
wait.

### 2. What went wrong?

**Failed operations**, with the server's own error code and sentence.

### 3. What is out there?

**The handsets** — when each last spoke to the server, which are revoked and why.

## Resolving a collision

<img src="https://mintcdn.com/assetinfinity/95UxrhuglB-erOSy/images/field/sync-conflict.png?fit=max&auto=format&n=95UxrhuglB-erOSy&q=85&s=4a64268cd81ee731a5253b08c8006cc2" alt="A sync conflict with both versions side by side" width="2880" height="1800" data-path="images/field/sync-conflict.png" />

The screen shows **both accounts** side by side: what the handset says, and what the server says,
field by field, with the fields that actually differ marked.

A typical collision:

> The handset says *"Gauge itself is out — 4.1 bar reading is the instrument."*
> The server says *"Vendor reports 4.1 bar is within tolerance for this model."*

Both are somebody's judgement. The system will not choose between them, and it should not.

You resolve it by choosing:

| Choice                         | Effect                                                            |
| ------------------------------ | ----------------------------------------------------------------- |
| **Keep the handset's version** | The technician's change is applied over the server's              |
| **Keep the server's version**  | The handset's change is discarded, with a record                  |
| **Merge**                      | Take some fields from each, where the collision is field-by-field |

Whatever you choose is recorded — who decided, when, and what was discarded. A resolution is a
decision with an author, not a silent overwrite.

## Automatic resolutions

Where two changes did not actually touch the same fields, the system resolves it by rule and says so
— including that it was automatic and which rule applied. These appear in the list as resolved
rather than being hidden, so the count of collisions is honest.

## Devices

Every enrolled handset: who it belongs to, when it last synced, how far behind it is, and whether it
is still usable.

<AccordionGroup>
  <Accordion title="Revoking a device">
    For a lost or stolen handset. The device can no longer sync and its sessions end immediately.

    **Work already queued on it is kept**, not discarded — those operations name the person who did
    them, and losing a phone should not lose a shift's records.
  </Accordion>

  <Accordion title="Requesting a wipe">
    Marks the device to erase its local database next time it connects. Use with revocation for a
    handset that has left the site.
  </Accordion>

  <Accordion title="A device that has not synced">
    A handset several days behind is usually a handset in a pocket, not a fault. One that is far
    behind and belongs to somebody on shift is worth a phone call.
  </Accordion>
</AccordionGroup>

## No charts here

The population is a plant's worth of handsets — tens, not thousands — and "which of these needs me"
is a list question. A dashboard over eleven devices would be decoration.


## Related topics

- [Signing in on the handset](/field/sign-in.md)
- [Finding your way around](/get-started/navigating.md)
- [People and access](/setup/access.md)
- [Working offline](/field/offline-and-sync.md)
- [Today and Work](/field/today-and-work.md)