Otto says a log line was blocked by a hook: "writing outside the performer's workspace folder" on a file it had just edited

Otto tried to add a line to a lead's log, then told you it was blocked by a hook with the error writing outside the performer's workspace folder, even though it had just edited that same file. Here is what happened and the update that fixes it.

What the message means

Booked Solid runs a safety check before Otto writes any file. One of its rules: Otto may only write inside your Booking HQ folder. A write anywhere else is refused with this exact message:

Blocked: writing outside the performer's workspace folder is not allowed.

In your case it fired by accident.

Why it refused a file Otto had just edited

Otto sometimes moves into one of your lead folders in the shell, for example to look at that lead's notes. Before version 1.11.109, the safety check measured your workspace from whatever folder Otto was standing in at that moment. So after one move into a lead's notes folder, the lead record one level up, the file Otto had just edited, counted as outside, and the log line was refused.

Nothing was lost. The edits that went through are saved. Only that log entry is missing.

Otto did not try another way around the block, and that is on purpose: lead records are never written from the shell, because a line written there is not checked before it lands.

The fix: update to 1.11.109 or newer

Since version 1.11.109, the check judges your workspace from the folder the session started in, which is your Booking HQ folder, wherever Otto moves afterward. Every newer version carries the fix too.

1. Click Check for updates in the top bar. Booked Solid also checks quietly every time it opens, and shows an Update ready badge when a new version has downloaded.
2. When the update window says the new version is ready, click Restart & install. The app reopens on the new version.
3. Open the Settings tab and find Updates. It reads You’re running Booked Solid, then the version number. It should be 1.11.109 or higher.

Each state of the update window is explained in How updates work: the update badge and Restart & install. If the app insists you are up to date when you are not, see Which version am I running.

Get the missing log entry back

Once you are updated, ask Otto to add the log entry it could not save. It goes through now. You can also type that line into the lead's log yourself.

If you still see the message after updating

On 1.11.109 or newer, this message means the file really is outside your Booking HQ folder, for example on your Desktop or in Documents. Otto can read your Desktop, Documents and Downloads, but it only writes inside your Booking HQ folder. A folder inside Booking HQ that is really a link to somewhere else counts as outside too. Ask Otto to save it inside your Booking HQ folder instead, then move it yourself.

Every refusal is noted, with the time and the file name, in guard-log.md inside the brain folder of your Booking HQ. Other blocks Otto may report are explained in "Blocked": the draft and file blocks explained.

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