Fix a folder that won't open or sync
Find the message a synced folder shows when it stops syncing, holds a change for you or leaves a file out, and fix it.
Start with marfa folders autostart status, which says whether the watch runs and why a folder isn't watched. Then marfa folders status ~/Documents/Home lists each file that isn't in step, and why. Find the message you see below.
Edits stop arriving
Read what marfa folders autostart status says:
folders do not sync: autostart is off, so runmarfa folders autostart on.the watch is not running: the last lines of the log it names on theit logs toline say why. On Linux, an earlier error is in the user journal:journalctl --user -u marfa-folder-watch.service.not watched, after a directory: the words in brackets say why, such as a first sync that waits formarfa folders confirm.
a large addition waits
a large addition waits: 55 new file(s) held, not sent; `folders confirm` sends them, and deleting the files you did not mean to add cancels it; new files that arrive meanwhile join itA large addition is more than 50 new files that are also more than a quarter of the folder's files. The rest of the folder goes on syncing. Delete the files you didn't mean to add, then run marfa folders confirm ~/Documents/Home, and the next push sends the rest. Deleting every held file cancels the addition.
a large removal waits
a large removal waits: 50 delete(s) not sent; `folders confirm` sends them, `folders restore` writes the files backA large removal is more than 100 files, or more than 10 that are over a quarter of the folder's files. Nothing is deleted yet. Run marfa folders restore ~/Documents/Home to get the files back, or marfa folders confirm ~/Documents/Home to bin their items at the next push. Renamed or moved files keep their items. A file confirm can't check, such as one in an unreadable folder, stays and shows not let go yet: confirm again once it's readable.
not taken
scan.pdf: not taken, it is empty, and a file item holds bytesmarfa folders status names each file the folder leaves out, and why: the file is empty, its name is one a secret goes by, or the folder's query holds no type the file would be, such as a PDF in a folder of notes. Add the file's contents, rename it, or widen the query.
another process is working this directory
One process works a directory at a time. A running watch lets a directory go when a command asks, so this usually means two watches: autostart's and one you started by hand. Stop the one you started, with Control+C.
If a command says a directory is held by another process, which did not let it go, it changed nothing: run it again.
the server asked for a wait before more is sent
the server asked for 60s before more is sent; push again after that to send the restYour instance is limiting requests, such as during the first sync of a large directory. Nothing is lost. Wait that long and push again. A running watch waits by itself.
was made by another build of marfa
A newer CLI can't open a directory's saved state that another build of marfa made. If it holds nothing still to send, the next push or watch replaces it and changes no file. Otherwise the CLI leaves the directory alone, and the message ends with what to do, usually to push the directory with the build that made its saved state, so the newer build can replace it.
is revoked, and a revoked folder has no settings to follow
The folder was retired everywhere, so this directory can't sync it. Run marfa folders remove ~/Documents/Home to keep its files as plain files.