> For the complete documentation index, see [llms.txt](https://help.usejimo.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.usejimo.com/docs/integrations/mcp/troubleshooting.md). # Troubleshooting Most issues resolve in one step. Find what you see in the left column. ## Connecting
What you seeWhat it usually means
The assistant reports "404" or "not found" when adding the connectorThe URL is missing /mcp. Use https://mcp.usejimo.com/mcp.
Approval page: "This connection request has expired"The request is older than 10 minutes, or the page was submitted twice. Start again from the assistant.
Approval refused for your accountYour Jimo role lacks Integrations access. Ask a workspace admin to grant it or to connect on your behalf.
"You have no project to connect yet"Finish setting up a Jimo project first.
Reconnecting fails with "scope was not registered"Your assistant registered Jimo with the older list of permissions. Remove the Jimo connector from the assistant, then add it again with https://mcp.usejimo.com/mcp.
The assistant was working and suddenly asks to sign in againThe connection was revoked from Settings, or the session expired. Connect again.
## Permissions | What you see | What it usually means | | --------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | The assistant says it lacks a permission (`INSUFFICIENT_SCOPE`) | That permission was not ticked at approval. [Connect again](/docs/integrations/mcp/connect-an-ai-assistant.md#connecting-again-or-connecting-another-project) and tick it, existing permissions are kept. | | The assistant can teach the agent but cannot create pages, skills, or put it live | **Build and run my Jimo Agent** was not approved. Connect again and tick it. | | Names and emails come back hidden | Your role, or the API key, does not include viewing end users' identities. | | An API key cannot set display rules, tags or a theme, or cannot publish | The key's Custom Access lacks **Create and edit experiences** or **Publish and pause experiences**. Permissions are fixed at creation: create a new key. See [API Keys for Automations](/docs/integrations/mcp/api-keys-for-automations.md). | | An API key cannot create or end an A/B test | Creating and ending a test needs a signed-in Jimo user. Run it from an assistant connected with your account. | ## Changes and Confirmations | What you see | What it usually means | | ------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | "Confirmation required" on a change | The assistant tried to confirm without a fresh preview, or the preview is older than 10 minutes. Ask it to preview again. | | A confirmation is refused after you agreed (`PREVIEW_STALE`) | The same setting changed in the dashboard after the preview. Ask the assistant to preview again. | | The preview warns that the experience was saved in the dashboard recently | Someone saved it in the dashboard in the last 30 minutes, and may still be editing it. Check with them before you confirm, or a dashboard tab left open could overwrite the change. | | "Experience not found" for a title you can see in Jimo | The name differs slightly. Ask the assistant to list experiences and use the exact title or the short reference it returns. | | Several matches for a name | The assistant asks which one. Answer with the reference it shows, or rename the duplicates in Jimo. | | "Monthly change limit reached" (`MCP_REQUEST_LIMIT_REACHED`) | The project's [monthly allowance](https://i.usejimo.com/settings/billing) is used up. Reading still works, and the allowance resets with billing. | ## Building and Editing Experiences | What you see | What it usually means | | --------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Publishing or pausing is refused at once, with no preview | Your plan does not allow it. The assistant follows the same plan rules as the dashboard, including how many experiences can be live at once (posts do not count). | | A resource center cannot be created | Your plan does not allow it from the assistant. Only the Ask AI part of a resource center needs the Jimo Agent, which every paid plan includes. | | An experience launched by another one also shows on its own | It has a trigger of its own. Set it to **No automatic trigger**, so it only shows when another experience launches it. **On manual trigger** is a different option. | | A tooltip became a cursor after drafting | Expected: on a button or a link, the draft review turns a tooltip into a cursor and drops its title and Next button. Ask the assistant to switch the step back to a tooltip if you want one. | | A trigger or a task condition is refused because the event does not exist (`EVENT_NOT_FOUND`) | The tracked event is not in the project yet, or its name differs. The assistant suggests the closest event name. Track the event first, or use the suggested one. | | The assistant asks for an element before it can pin a step | Tooltips, hotspots, cursors, and hints need an element of your app, never a CSS selector. Capture it in your app, see [Pinning steps to your app](/docs/integrations/mcp/what-to-ask.md#pinning-steps-to-your-app). | | A captured element matches several places on the page | Capture something more specific, or add a `data-jimo-id` attribute to the element and capture it again. | | An edit to a published experience is refused because it changed | Someone edited the experience after the assistant read it. Ask the assistant to read it again and redo the edit. | | An edit of many steps is refused whole | One edit in the call has a problem, so nothing was applied. A call takes up to 50 edits: the assistant fixes the faulty one, or splits the work. | | Styling made in the builder is gone after applying a theme | Applying a theme replaces the experience's styling, the way the dashboard does. Restyle it in the builder if needed. | | An A/B test does not start | The test starts only on a live experience. Publish the original first. Tests are not available on changelog posts. | ## Setting Up the Jimo Agent | What you see | What it usually means | | ------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Putting the launcher live is refused | Your plan does not include the Jimo Agent. The preview also lists what is still missing in the setup. | | A URL rule is refused | It did not match the example URLs the way it was described. For launcher targeting and website filters, write a path such as `/docs`, not a full address. For a screen that routes in its `#` fragment, write the rule on the full URL. | | A batch of pages or skills is refused (`BATCH_ITEMS_REFUSED`) | At least one item has a problem, so nothing was saved. The assistant lists each item with why, fixes them, and sends the batch again. | | "Page name taken" (`PAGE_NAME_TAKEN`) | Page names are unique in the project, case ignored. Pick another name or update the existing page. | | A fifth suggestion is refused (`SUGGESTION_ACTIVE_LIMIT`) | A page has at most four active suggestions. Deactivate one to add another. | | A knowledge source cannot be deleted | It is still training. Wait until training finishes, then delete it. | ## Analytics | What you see | What it usually means | | ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------- | | Analytics come back as "not measured" | The analytics backend was unreachable at that moment. Retry later. It is not a zero. | | The agent's success rate looks low | It is likes against dislikes, and conversations nobody reacted to do not count. A handful of reactions can move it a lot. | ## Still Stuck? Contact with the assistant used, the project name, the request you made, and the error text. {% hint style="danger" %} Never share a Client secret with anyone, including support. {% endhint %} ## Next Steps * [Connect an AI Assistant](/docs/integrations/mcp/connect-an-ai-assistant.md): the full connection flow. * [Managing Access, Usage & Limits](/docs/integrations/mcp/managing-access-usage-and-limits.md): revoking, rotating, and the monthly allowance.