> ## Documentation Index > Fetch the complete documentation index at: https://docs.diversion.dev/llms.txt > Use this file to discover all available pages before exploring further. # Sync status > What each sync status in the desktop and web app means, and what to do about it Diversion shows sync status in two places: the **workspace header** at the top of an open repo, and each workspace's row on the dashboard's **Local Workspaces** tab (click the Diversion logo at the top left to open the dashboard). The two use different labels -- find the one you're looking at below. For the command line, see [`dv status`](/cmd-ref/status). ## Workspace header The header reports two separate facts, one per line: | Line | What it tells you | | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | First line | What's happening to the files on this machine, and the commit they're synced to | | Second line | `cloud workspace dv.commit.` -- the commit your cloud workspace is on, sometimes followed by a [note about the branch](#notes-on-the-second-line). After an error stops sync, the error takes this line instead | When both lines name the same commit, the files on this machine match your cloud workspace. These are the same two commits `dv status` prints. A status stays on screen until the state changes, and a button appears next to it only when there's something for you to do. If the header is too narrow for the whole second line, hover over the status to read it. | First line | What to do | | ----------------------------------------------------------------------------------------- | ------------------------------------------------------------ | | [Synced to `dv.commit.`](#synced) | Nothing | | [Syncing to `dv.commit.`](#syncing) or **Syncing…** | Keep editing -- wait to commit | | [Sync paused at `dv.commit.`](#sync-paused) | Click **Resume** | | [Paused by error at `dv.commit.`](#paused-by-error) | Click **View error**, then **Resume** | | [Sync error at `dv.commit.`](#sync-error) | Click **View error** | | [Agent not running](#agent-not-running) | Click **Start agent** | | [Starting Diversion agent…](#agent-starting-or-updating) or **Updating Diversion agent…** | Nothing -- keep working | | [Agent outdated](#agent-outdated) | Click the Diversion logo at the top left, then **reinstall** | | [Cloud workspace `dv.commit.`](#cloud-workspace) | Nothing -- no files on this machine to report on | ### Synced Workspace header reading Synced to dv.commit.12345, cloud workspace dv.commit.12345, branch has no newer commits **Synced to `dv.commit.`** means there's nothing left to transfer, and the files on this machine match that commit. Hover over it to see the most recent change synced in each direction. The cloud icon turns green only when the files on this machine, your cloud workspace and the branch are all on the same commit. Otherwise it stays grey -- when the branch has [newer commits](#newer-commits-on-the-branch), or for a few seconds after your workspace moves to a new commit, until the two lines catch up. Workspace header with a grey cloud icon, reading Synced to dv.commit.68050, cloud workspace dv.commit.68053, branch has no newer commits Right after the agent starts, the status can read just **Synced**, without a commit, until the agent reports one. **What to do:** Nothing. ### Syncing Workspace header reading Syncing to dv.commit.12345, 3 files remaining **Syncing to `dv.commit.`** means files are still moving between this machine and the cloud. The second line counts the files remaining. When there's no commit to name, it reads **Syncing…** instead. Hover over it to see how many files and how much data have transferred so far. If the branch also has newer commits, the file count is followed by a [note about the branch](#notes-on-the-second-line). **What to do:** Keep editing -- your changes are picked up as you save. Wait to commit: while sync is running the **Commit** button is disabled, along with switching branches, merging, reverting, cherry-picking and shelving. They become available again when sync finishes. ### Newer commits on the branch When someone commits to your branch, the second line says so. What it says depends on your workspace's [automatic update](/concepts/syncing#workspace-automatic-update) setting. **Automatic update on** Workspace header reading Synced to dv.commit.68053, cloud workspace dv.commit.68053, updating to dv.commit.68056 `updating to dv.commit.` means your cloud workspace is moving to the branch's newest commit by itself, and the files on this machine follow. **What to do:** Nothing. **Automatic update off** Workspace header reading Synced to dv.commit.68053, cloud workspace dv.commit.68053, automatic update is off, with an Update to dv.commit.68056 button `automatic update is off` means the branch has newer commits, and your workspace waits until you update. **What to do:** Click **Update to `dv.commit.`**, or run `dv update`. The button reads **Updating workspace…** while the update runs. Workspace header with the button reading Updating workspace… **Conflicts stopped the update** Workspace header reading Synced to dv.commit.68053, cloud workspace dv.commit.68053, branch is at dv.commit.68056, with a Resolve conflicts to update button `branch is at dv.commit.` with a **Resolve conflicts to update** button means the automatic update stopped because the newer commits conflict with changes in your workspace. **What to do:** Click **Resolve conflicts to update** to open the merge, then resolve the conflicts. See [Merge conflicts](/concepts/conflicts#merge-conflicts). ### Sync paused Workspace header reading Sync paused at dv.commit.68053, cloud workspace dv.commit.68053, branch is at dv.commit.68056, with a Resume button **Sync paused at `dv.commit.`** means no files move in either direction, because you turned sync off. The commit is the last one this machine synced. The agent can also stop sync by itself after a failure -- that reads differently, see [Paused by error](#paused-by-error). While sync is paused, has an error, or the agent isn't running, the header offers only the fix. **Update** stays hidden, because updating moves your cloud workspace while no files reach this machine. **What to do:** Click **Resume**. Committing is disabled while sync is paused, along with switching branches, merging, reverting, cherry-picking and shelving -- they come back once sync is running. See [Pause/Resume sync](/basic/sync-pause-resume). ### Paused by error Workspace header reading Paused by error at dv.commit.68053 in red, with the error on the second line and View error and Resume buttons **Paused by error at `dv.commit.`** means the agent stopped sync after a failure. The status is red rather than the grey of a pause you switched on, and a **View error** button appears next to **Resume**. The error takes the second line, and the cloud workspace commit moves into the tooltip -- hover the status to read it. **What to do:** Click **View error**, fix what it reports, then click **Resume** -- resuming without fixing the cause stops sync again. The same actions are unavailable as for a pause you switched on. ### Sync error Workspace header reading Sync error at dv.commit.68053, cloud workspace dv.commit.68053, branch is at dv.commit.68056, with a View error button **Sync error at `dv.commit.`** means the agent hit a problem syncing this workspace. The commit is the last one this machine synced. **What to do:** Click **View error** to read the full message. ### Agent not running Workspace header reading Agent not running, last synced dv.commit.68053, branch is at dv.commit.68056, with a Start agent button **Agent not running** means the Diversion agent, which syncs your files in the background, isn't running on this machine, so nothing syncs. The second line shows the commit this machine was **last synced** to. **What to do:** Click **Start agent**, or run `dv` in a terminal. ### Agent starting or updating Workspace header reading Updating Diversion agent…, last synced dv.commit.68053, branch is at dv.commit.68056 **Starting Diversion agent…** or **Updating Diversion agent…** means the agent is starting up or installing an update. Sync resumes when it's done. **What to do:** Nothing -- keep working, and don't start the agent again. Changes you make in the meantime sync once it's back. ### Agent outdated Workspace header badge reading Agent outdated **Agent outdated** appears in the desktop app, next to the sync status, when the agent on this machine is older than the app needs. **What to do:** Click the Diversion logo at the top left to open the dashboard, then click **reinstall** in the outdated-agent notice. Reinstalling clears the agent's record of the workspaces on this machine, so finish or pause what you're doing first. The files stay where they are, but each workspace has to be attached again before it syncs: on the same dashboard, click **Attach workspace**, choose the workspace's folder and click **Connect**. ### Cloud workspace Workspace header reading Cloud workspace dv.commit.68053 **Cloud workspace `dv.commit.`** is the web app's view. The web app can't see the files on your machine, so it shows only the commit your cloud workspace is on, and never **Synced**. The desktop app shows the same for a workspace that isn't cloned to this machine. A [note about the branch](#notes-on-the-second-line) can follow on the second line, with an **Update to** button when automatic update is off. The status reads **Syncing…** while changes upload to the workspace. **What to do:** Nothing. To check a machine's files, open the workspace in the desktop app on that machine. ### Notes on the second line | Note | What it means | | ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `branch has no newer commits` | Your cloud workspace is on the branch's newest commit | | `updating to dv.commit.` | Automatic update is moving your cloud workspace to the branch's newest commit | | `automatic update is off` | The branch has newer commits -- click **Update to** to get them | | `branch is at dv.commit.` | The branch has a newer commit than your cloud workspace. Shown while sync is stopped, or when conflicts stopped the update | | `files on this machine are not up to date` | Sync is stopped, and your cloud workspace moved to another commit without this machine -- automatic update keeps moving it while sync is stopped. The files here catch up once sync runs again | | `last synced dv.commit.` | The agent isn't running -- the last commit this machine synced | ## Dashboard workspace row To open the dashboard, click the Diversion logo at the top left. Its **Local Workspaces** tab shows a shorter status on each workspace's row. It doesn't name a commit -- open the workspace to see which commit its files are on. **Synced** Dashboard workspace row reading Synced Nothing is left to transfer for this workspace. **What to do:** Nothing. **Syncing** Dashboard workspace row reading Syncing Scan in progress **Syncing…**, or **Syncing** followed by what the agent is doing -- such as scanning the folder or transferring a file. **What to do:** Keep editing -- wait for it to finish before committing. **Sync paused** Dashboard workspace row reading Sync paused, with the Sync toggle off You turned sync off for this workspace, so no files move. **What to do:** Turn the **Sync** toggle back on. **Paused - ``** Dashboard workspace row reading Paused - Access denied, with a red pause icon and the Sync toggle off The agent stopped sync after a failure and named the cause, and the pause icon is red. No files move until it runs again. **What to do:** Click the label to read the full message, fix what it reports, then turn the **Sync** toggle back on -- turning it on without fixing the cause stops sync again. **Sync error** Dashboard workspace row reading Sync error: Access denied **Sync error:** followed by the error. **What to do:** Click the label to read the full message. **Agent down** Dashboard workspace row reading Agent down The Diversion agent isn't running on this machine, so none of its workspaces sync. **What to do:** Click **Start agent** in the notice the app shows, or run `dv` in a terminal.