Troubleshooting
The errors a connected assistant can run into, what each means, and what to do.
"… is not available through algomo_read; call it through algomo_edit"
The assistant sent an operation to the wrong tool. Each operation belongs to exactly one of the four, and the refusal names the right one. Nothing ran. The assistant retries through the named tool; if it keeps choosing wrong, tell it which tool to use.
"Invalid operation input"
The operation's fields did not match its schema; the error lists the field and what was wrong. The assistant fetches the schema with { "op": "schema", "target": { "op": "…" } } and retries. Nothing ran.
Writes refused because onboarding is required
The workspace has not completed onboarding. Reads work; writes do not until the spec and the build plan are in. See Set up a new workspace.
"Session not found"
The session was published or discarded, by you, by someone else in the workspace, or by the assistant in an earlier conversation. session:list shows the sessions that exist. Open a new one for further changes.
A publish refused with conflicts
Someone saved the same entity after the session was opened, so the session's copy is out of date. The save changes nothing in that case. Open a fresh session and stage the change again; session:diff on the old one shows what it held.
A publish refused with validation errors
The staged configuration is invalid: a goal with no instructions, a tool the chatbot references that no longer exists, a workflow with a broken reference. The errors name the entity and field. Fix them in the same session and publish again; session:validate runs the same checks without saving.
The assistant says it is not signed in
The sign-in expired or the connector was removed. Reconnect in your client: in Claude Code, /mcp and choose Algomo; in Claude or ChatGPT, open the connector and sign in again.
The assistant works on the wrong workspace
The connection is scoped to the workspace picked at sign-in. Remove the connector and add it again, picking the right workspace, or add a second connector under another name.
A workflow run did something you did not expect
A run through the connection does what the workflow does, including its emails and messages. Check the run's trace: workflow:getRun returns every step with its input and output.
Still stuck
Email support@algomo.com with the name of the workspace, the operation that failed and the error text as the assistant showed it. Support lists what else helps.