Archiving a lead fails with an EPERM error: your Booking HQ is inside OneDrive

You tried to archive a few finished leads to keep the board lean, and the archive failed on every one of them with an EPERM error. The note that came back read Archive copy failed (EPERM...); original untouched. You left it, came back, tried again, and nothing changed: the lock hasn't cleared in two days. If you have already spotted OneDrive in the picture and called it a OneDrive-lock EPERM error, you have the cause exactly right. Here is why nothing was lost, why the app stopped on purpose, and how to make it stop happening.

First: no data was lost

Every lead you tried to archive is exactly as it was, and not one of them lost a single line. Notes, messages, dates, stage history: all of it is still sitting in your active leads. The only thing that did not happen is the board trim, which is cosmetic. There is nothing to recover and nothing to re-enter.

What EPERM means

EPERM is short for "operation not permitted". It is the operating system saying it cannot touch a file right now, not the app saying it refuses to. Something else on your computer is holding that file, and in these reports the something is OneDrive. Your Booking HQ folder is sitting inside OneDrive, and OneDrive keeps a lock on the lead files while it syncs them.

You can confirm that in a few seconds. Open Settings > General > Your Booking HQ and read the path in the box at the top of that card. If OneDrive appears anywhere in it (something like C:\Users\you\OneDrive\Documents\Booking HQ), that is your answer.

Why Otto stops instead of pushing through

Archiving a lead is deliberately careful, and the order of operations is what explains the error. Otto does three things, in this order:

1. Copies the whole lead folder into archive. Not a summary of it, the whole record.
2. Verifies that copy, checking every file that landed against the original, not only the main lead file.
3. Only then removes the original.

A lead is never taken off your board until a verified copy is already sitting safe in the archive. When OneDrive has those files locked, step 1 cannot finish. So Otto stops right there, clears away the half-written copy, and leaves the original alone. That is the app protecting your record, not a glitch, and it is why the failure note ends with original untouched.

Waiting for the lock to clear is a dead end

Almost everyone tries this first: leave it a day, come back, run the archive again. Skip that step. This lock is not a leftover from something that crashed, the kind a reboot tidies up. It comes back because the folder lives inside OneDrive full time, so OneDrive is syncing those files again as soon as anything touches them. That is exactly why the same leads still fail two days later, and why they would still fail next week. Retrying on its own changes nothing. Either the folder moves, or OneDrive has to be told to leave it alone.

The permanent fix: move your Booking HQ out of OneDrive

A plain local folder makes every save and every archive run lock free, and it retires this whole class of error for good. The order matters, so do not skip step 1.

1. Quit Booked Solid completely. Not minimised, fully closed. Moving the folder while the app is still reading from it is how a clean move turns into a mess.
2. In File Explorer, move your Booking HQ folder out of OneDrive to a normal local spot, for example a folder in Documents or on the Desktop that is not inside the OneDrive folder. Moving it is safe. The app only points at that folder, it keeps no second copy anywhere else, and nothing outside the folder needs it to stay where it was. Your leads, your notes and your archive all travel with it.
3. Reopen Booked Solid, go to Settings > General > Your Booking HQ, and click Find my existing Booking HQ. If it turns one up it shows you what it found, with a count of the leads inside so you can tell it is the right one. If it does not, it opens a folder picker so you can point at the new location yourself. Either way, confirm with Use this one. That adopts your existing Booking HQ in place, so nothing is re-imported, nothing is duplicated and nothing is lost. You can also skip the search entirely: click Change next to the path and pick the folder directly.
4. Run the archive again on the same leads. They move cleanly this time.

If you want to stay in OneDrive for now

Two workarounds free the lock long enough for the copy to finish. Either one works, and neither is a cure.

• Right-click the Booking HQ folder in File Explorer and choose Always keep on this device, which tells Windows to hold real local copies of everything in it instead of fetching them on demand.
• Or pause OneDrive syncing for a minute, then run the archive.

Be clear about what those buy you: one clean run. The folder is still inside OneDrive, so the lock comes back, and you are doing this again before the next archive. Moving the folder out is the real cure.

OneDrive is not the only thing that does this

Dropbox, Google Drive and any network drive hold the same class of lock for the same reason, and antivirus real-time scanning can hold it too while it scans a file. If your Booking HQ sits in one of those, everything above applies with the name swapped. A plain local folder on this computer is the only home that avoids it entirely. If what you want is cloud copies of your work, use the app's own automatic backups for that instead of putting the live folder inside a sync folder. There is more on choosing, moving and restoring that folder in Your Booking HQ folder: change it, find it, restore a backup, tune it up.

What the message looks like depends on your version

From version 1.11.29 onward the app recognises a sync lock and says so in the note itself: it names OneDrive, Dropbox and network drives, mentions antivirus, and tells you that moving your Booking HQ to a plain local folder clears it. On older builds you get only the raw form, Archive copy failed (EPERM...); original untouched, with the operating system's own wording inside the brackets and no hint about what to do. If that is what you are looking at, click Check for updates in the top bar, or take the newest build from booked.kivimedia.co/download.

One deliberate limit is worth knowing. The app adds that plain-language hint only for lock-class errors, which are EPERM, EBUSY and EACCES. That is on purpose, so a real disk fault is never mislabelled as a OneDrive problem. If your archive fails with a different code (a full disk shows up as ENOSPC, for instance), OneDrive is not your culprit and moving the folder will not help. Send that note to us instead.

Two things to watch for

• A lead that shows up twice. If a lock lands after the copy has already been verified but before the original is removed, the lead can end up in both your active leads and your archive. If you see a duplicate after an archive attempt, do not delete either copy by hand. Send us a ticket with the lead's name and we will tell you which copy to keep.
• Nothing warns you at setup. The app does not stop you from choosing a Booking HQ inside OneDrive, Dropbox or a network drive, so that check is yours to make. Settings > General > Your Booking HQ shows the exact folder in use.

Pulling a lead back out of the archive hits the same wall

Restoring an archived lead uses the same copy, verify, then remove sequence, so a sync lock stops it the same way, with a note that starts Restore copy failed. Same cause, same fix, and the archived copy stays where it is in the meantime.

If it is your gig saves failing rather than archiving

The same lock breaks saves. When saving a gig comes back with The record could not be saved, so nothing was changed, or a stage change comes back with The stage change could not be saved, so nothing was changed, followed by a reason you cannot act on, check the same three things the app names there: that your disk is not full, that your Booking HQ is a plain local folder and not inside OneDrive, Dropbox or a network drive, and that antivirus is not locking it. Nothing is lost in that case either. A failed save is rolled back, so the record stays exactly as it was before you edited it.

If it still does not work

If the leads still refuse to archive after the folder has moved, send us a ticket and include three things: the exact failure note including the error code in the brackets, the path shown in Settings > General > Your Booking HQ, and your app version. A failure that survives a move out of OneDrive is a different problem and we want to see it.

Still stuck? Email bookedsolid@kivimedia.freshdesk.com and a person will help.