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

# Sync status

> Understand waiting, queued changes, conflicts, and stopped services.

For a paired machine, **Connections** shows a recent health snapshot. The
desktop tray and `nlkb doctor` provide local status. The web inventory reports
health; it does not start the machine's service.

| State or symptom            | What to check                                                                                                                |
| --------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| In sync                     | The replica has caught up to the reported cloud state.                                                                       |
| Waiting / no first activity | Finish enrollment and start the background service.                                                                          |
| Catching up / uploading     | Let downloads or queued uploads complete; check again if progress stops.                                                     |
| Paused                      | Resume when ready. Local changes can continue to queue while transfer is paused.                                             |
| Stale                       | The replica has not reported recently; check connectivity and the service. Replica presence becomes stale after ten minutes. |
| Conflicted                  | Review the retained competing versions in Conflicts.                                                                         |
| Diverged or unhealthy       | Run diagnostics and inspect the specific mount error before changing files.                                                  |
| Revoked or access removed   | Ask the connection owner or vault admin to check permissions. A revoked connection needs replacement.                        |

## First checks on the machine

```sh theme={null}
nlkb doctor
nlkb service status
nlkb status --json
```

If the service is stopped and the replica is already enrolled:

```sh theme={null}
nlkb service start
nlkb doctor
```

Do not run a second `nlkb sync` while the background service is watching the
same replica.

## Offline work and pause

Local changes are queued durably and sent after connectivity returns. Use the
local editor for offline files; the web/desktop viewer still depends on its web
service. Pause stops network transfer while local watching and queueing
continue. Stopping the daemon is a separate operation.

## Missing folder or invalid content

A missing or unreadable mount pauses that mount instead of automatically
interpreting every file as deleted. Restore the expected folder or follow the
diagnostic's recovery path. Do not recreate an empty mount and force deletion to
make an error disappear.

Symlinks are not followed. Invalid names, unsupported files, oversized bodies,
or failed integrity checks need repair. Preserve local work and ask support
before resetting client state or removing quarantined material.

On Linux containers without a service manager, service persistence is limited to
the host/container lifetime. After recycle, run `nlkb service start` or
configure the host to run the daemon.