Troubleshooting translations and assistant connections

Documentation / Saving, recovery, and troubleshooting

First decide whether the problem concerns content selection, translation generation, or the assistant connection itself. Record the website, page ID, language, client, and redacted error. Do not repeatedly generate translations or reconnect credentials before identifying which stage failed.

Check the language target

Translations share the source page ID but have separate language variants. Confirm the website's main and configured languages and the requested lang on assistant calls. A fallback can show source content when the expected translation is absent; the CMS interface language is not proof of the page's content language.

Custom-page translation uses saved source, not unpublished custom-design drafts. It preserves structure and translates supported text and reader-facing attributes. If validation rejects an incomplete response, inspect the error rather than saving a partial translation by hand.

Legal generation has a separate translation stage. Additional languages require a configured workspace provider, and all required translations must succeed before legal page writes start.

Check connection access

The hosted MCP URL is https://mcp.beeboo.app/mcp, with authorization at https://auth.beeboo.app. Verify the client plan and workspace approval. ChatGPT's current full MCP support is documented for Business and Enterprise/Edu on the web; Claude has its own personal-plan and organization controls.

For 401 errors, check authentication and expiry. For 403 errors, check read/write scopes and current website membership. A listed tool can still be forbidden. Local VS Code stdio uses a privately supplied PAT; hosted connections use OAuth consent.

Refresh safely

After a server update, restart or refresh the client tool list as appropriate. ChatGPT workspace apps can retain an approved tool snapshot until an administrator refreshes it. Reconnect only when needed, and revoke obsolete access separately.

Share no token, sign-in code, callback secret, or private customer content in troubleshooting messages. See languages and translations and agentic editing and connections.