When something goes wrong
Most of what goes wrong falls into a handful of shapes. Here is what each one is and what to do about it.
Signing in
The link has expired or has already been used. Sign-in links are single-use and short-lived. Ask for a new one; if you clicked the old one on a different device, that counts as using it.
The invite code will not work. Codes have a limited number of seats. If yours is full, try another, or leave your email and you will hear when seats open.
The workspace
"Initializing workspace…" appears when a workspace is being prepared. It takes a few seconds. If it stays much longer than that, reload the page.
"Connection lost" means the browser cannot currently reach the server. The page retries by itself and picks up where it was, including work an agent was in the middle of. Reloading is safe.
An error card with a code. Something failed on our side and has been logged automatically. The code identifies your specific failure, so include it if you write to us — with it, the problem can be found in minutes.
The agent
It stopped mid-work. Ask it to continue. Work in progress is recorded as it goes, so it resumes rather than starting over.
It says the credit budget is spent. Agents stop at zero — chat included — until the monthly allowance resets or you top up. See credits and plans.
It cannot use a tool. Usually an expired or revoked credential. Reconnect the tool; the agent will normally have left a blocked item in your inbox naming the tool and the step it stopped at.
It is doing the wrong thing, repeatedly. Not really an error — it is a correction that did not stick. Ask what it has on record about how you want the work done; the answer usually explains it. Reviewing and correcting work covers the fix.
It says something is impossible. Worth a second question. Ask whether a tool exists for it in the catalogue: "not possible" is sometimes "not connected".
It invented something. Ask where a fact came from. Where the answer is unsatisfying, say so plainly and, if it matters, record the correct version as a memory so it does not come back.
The workspace itself went wrong
If a piece of work is wrong, correct it in the chat. If the last stretch went sideways and you want the workspace as it was, restore a checkpoint — you will be shown what changes before anything happens.
Getting help that leads somewhere
Write to us through the contact form. Three things turn a slow exchange into a fast one: what you were doing, what happened instead, and the code from the error card if there was one. Roughly when it happened helps too.
If the problem is that BossForce did something you did not expect rather than that it broke, say so anyway. The awkward feedback — this was confusing, this took too long, I did not understand what it was doing — is the useful kind, and there is a good chance your agent will ask you for exactly that in your first week.