dv status.
Workspace header
The header reports two separate facts, one per line:
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.
Synced
Synced todv.commit.<id> 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 the same colour as the text — when the branch has newer commits, or for a few seconds after your workspace moves to a new commit, until the two lines catch up.
Right after the agent starts, the status can read just Synced, without a commit, until the agent reports one.
What to do: Nothing.
Syncing
Syncing todv.commit.<id> 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.
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.
Before any file is queued, the agent has work to do that isn’t a transfer. The second line names that work instead of counting files. As soon as files are queued, the line counts them again.
Checking for changes…
The agent is reading the workspace folder to find what changed since the last sync. This is the one you see most often. On a small workspace it finishes in well under a second, so you may never catch it.
What to do: Keep editing — wait for it to finish before committing.
Cloning…
The agent is cloning the repo to this machine. It shows only until the file count begins.
What to do: Wait for it to finish.
Updating ignore rules…
You changed .dvignore, and the agent is applying it, so the files it now covers stop syncing. A rule that newly covers thousands of files can hold this for a minute. See The .dvignore file.
What to do: Keep editing — wait for it to finish before committing.
Applying selective sync…
You changed which folders this machine keeps, and the agent is adding or removing them. See Selective sync.
What to do: Keep editing — wait for it to finish before committing.
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 setting. Automatic update onupdating to dv.commit.<id> 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
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.<id>, or run dv update. The button reads Updating workspace… while the update runs.
Conflicts stopped the update
branch is at dv.commit.<id> 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.
Sync paused
Sync paused atdv.commit.<id> 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.
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.
Paused by error
Paused by error atdv.commit.<id> means the agent stopped sync after a failure. The pause icon and its background are red rather than the purple 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
Sync error atdv.commit.<id> 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
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 rundv in a terminal.
Agent starting or updating
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
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
Cloud workspacedv.commit.<id> 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 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
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 Nothing is left to transfer for this workspace. What to do: Nothing. Syncing Syncing…, or Syncing: followed by the number of files remaining or the name of a file it’s transferring. What to do: Keep editing — wait for it to finish before committing. Syncing: Checking for changes… The agent is finding what changed since the last sync. What to do: Keep editing — wait for it to finish before committing. Syncing: Cloning… The agent is cloning the repo to this machine. What to do: Wait for it to finish. Syncing: Updating ignore rules… The agent is applying your.dvignore changes. What to do: Keep editing — wait for it to finish before committing.
Syncing: Applying selective sync…
The agent is adding or removing the folders you changed in selective sync. What to do: Keep editing — wait for it to finish before committing.
Sync paused
You turned sync off for this workspace, so no files move. What to do: Turn on the toggle to the right of the status, just left of the ⋯ menu. Its tooltip reads Resume sync.
Paused - <error>
The agent stopped sync after a failure and named the cause. 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 toggle back on — turning it on without fixing the cause stops sync again.
Sync error
Sync error: followed by the error. What to do: Click the label to read the full message.
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 at the top right of the app, or run dv in a terminal.