> 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/settings/troubleshooting.md).

# Troubleshooting

Where to start when something does not work, and the reference for the Troubleshoot tool: how to open it, what it shows, the two reset actions.

Start from the symptom: most problems have a dedicated page, listed below. The rest of this page is the reference for the Troubleshoot tool, which shows on your own app why each experience shows or not.

## Start from the symptom

| Symptom                                                    | Go to                                                                                                                                              |
| ---------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| An experience is published but does not show on your app   | [Why my experience does not show](https://help.usejimo.com/docs/getting-started/publish-your-first-experience/why-my-experience-does-not-show.md)  |
| The Chrome extension does not open the builder on your app | [When the extension does not load](https://help.usejimo.com/docs/getting-started/install-the-chrome-extension/when-the-extension-does-not-load.md) |
| Your AI assistant shows an error when it uses Jimo         | [MCP troubleshooting](https://help.usejimo.com/docs/integrations/mcp/troubleshooting.md)                                                           |
| The MAU count is higher than your real users               | [MAU](https://help.usejimo.com/docs/settings/mau-monthly-active-users.md)                                                                          |
| Jimo does not start on your app at all                     | [Install Jimo, Verify](https://help.usejimo.com/docs/getting-started/install-jimo.md#verify)                                                       |
| A tour step cannot find its element                        | [Stable selectors](https://help.usejimo.com/docs/getting-started/create-your-first-experience/stable-selectors-on-a-dynamic-front-end.md)          |

**From your assistant:** "Which experiences had steps whose element could not be found in the last 30 days?" See [What to ask](https://help.usejimo.com/docs/integrations/mcp/what-to-ask.md).

## Open the Troubleshoot tool

The tool opens on top of your app, on a page where the snippet runs. Three ways in.

{% tabs %}
{% tab title="From Settings" %}
Go to **Settings > Troubleshoot** (`/settings/troubleshoot`), enter the URL of a page of your app in the **Go to** field, and click **Start Troubleshooting**: a new tab opens with the tool on top of the page.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FaZ7C96BusmUfsrmDO1v7%2FE2-r03-settings-troubleshoot.png?alt=media&amp;token=4b63dad8-5563-468d-8046-f203dc2da8d6" alt="Settings, Troubleshoot: the Go to URL field above Start Troubleshooting (A) and the Launch using keyboard shortcut toggle (B)"><figcaption></figcaption></figure>
{% endtab %}

{% tab title="From an experience" %}
Open a live experience in the dashboard. On its page, click **...** at the top right, then **Troubleshoot**, and enter the URL it runs on. The tool opens focused on that experience. The **...** menu of the experience cards in the list does not have this entry.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FOiVq3QqTYBT4Mjgkm5sz%2Ftroubleshoot-06-experience-more-menu.png?alt=media&amp;token=d34a0af0-aa5b-4b67-ba1d-eb605b871efe" alt="The more menu at the top right of a live experience page, with Edit, Duplicate, Public URL, Troubleshoot and Delete"><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Keyboard shortcut" %}
Turn on **Launch using keyboard shortcut** once in **Settings > Troubleshoot**. Then, on any page of your app where Jimo runs, press `Cmd Shift L` on Mac or `Ctrl Shift L` on Windows and Linux. While the toggle is off, the shortcut does nothing. Once it is on, anyone browsing your app can use the shortcut, not only your team: turn it off when you are done testing.
{% endtab %}
{% endtabs %}

#### When the tool does not open

The tool needs a working snippet. If it does not open, Jimo is not running on this page: the snippet is missing, the page is excluded by manual initialization, Force Identify is on and no identify call ran, or a Content Security Policy blocks the script. See cause 5 in [Why my experience does not show](https://help.usejimo.com/docs/getting-started/publish-your-first-experience/why-my-experience-does-not-show.md).

## What the tool shows

The tool is a widget you can drag anywhere on the page and close with its close button.

#### User panel

The current Jimo user's name sits at the top of the tool. Click it to open the user panel: the two [reset actions](#reset-user-activities), the segments the user belongs to, and their attributes with their current values. The back arrow returns to the experience list. Use it to check that the identify call ran and that the attributes your targeting needs are there.

#### Experience list

Every published experience available on this page, with a search bar and the tabs **All**, **Shown**, **Waiting** and **Ineligible**. Expand an experience to see a one-line result, such as **Some conditions are not matched**, then each check with a tick when it passes or a warning when it fails, a **Learn more** link to the matching help page, and the experience ID, which opens it in the dashboard.

#### Statuses

| Status         | Meaning                                                                                                                                               |
| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Shown**      | On screen now. The result reads **Experience is currently being shown**.                                                                              |
| **Seen**       | Already seen, dismissed or completed by this user.                                                                                                    |
| **Waiting**    | Eligible, waiting for its trigger (**Waiting for custom trigger**, **Waiting for URL trigger**), or for another experience that goes first.           |
| **Ineligible** | At least one check fails, such as **Didn't match user segment** or **Don't match current URL**. The result reads **Some conditions are not matched**. |
| **Pending**    | Hints only. The hint is published and none is on screen yet. The result reads **No hint is on screen**.                                               |

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FWTbbk90MY6ymGfb9tQHq%2Ftroubleshoot-04-status-to-check.png?alt=media&amp;token=744cd7f3-42bb-4dda-b642-3267515628b6" alt="Five statuses and what to check next: Shown, nothing to fix; Seen, reset activities; Waiting, Show on and priority; Ineligible, Who, Where and Env; Pending, selector and issues"><figcaption></figcaption></figure>

#### Another experience goes first

When an experience waits behind another one, its result reads **Another experience goes first:** followed by the name of that experience. The name is plain text, not a link: search for it in the list to see its own status. Read the checks under the result too, since a failed check can point to another cause at the same time, such as **Experience is scheduled**.

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FGBHBUuczSDrkKMIAL7jX%2Ftroubleshoot-01-blocking-relation.png?alt=media&amp;token=31ab4ef0-8287-4399-8bbc-873e99031351" alt="Troubleshoot tool: a waiting tour expanded, its result reads Another experience goes first: Profile Page Quick Guide, above a passed URL check and a failed Experience is scheduled check"><figcaption></figcaption></figure>

#### A hint whose element is not found

A hint reads **Pending** while no hint is on screen. When the element it is pinned to cannot be found, an issues count shows next to the status, and the detail names the hint and its selector, for example **On Hint 1, element not found using selector** `body > h1`. The same failure is reported in the experience's issues. Fix the selector as described in [Stable selectors](https://help.usejimo.com/docs/getting-started/create-your-first-experience/stable-selectors-on-a-dynamic-front-end.md).

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FUH55JkJBftH40BxM2xTV%2Ftroubleshoot-03-hint-element-not-found.png?alt=media&amp;token=9d8b0a08-6f01-42c8-aaaf-fa460c10bb50" alt="A hint in the Troubleshoot tool with the Pending status and 1 Issues, its result No hint is on screen and the detail On Hint 1, element not found using selector body > h1"><figcaption></figcaption></figure>

#### Content Security Policy violations

The tool reports CSP violations it detects on the page, so a blocked resource shows up here instead of as a widget that stays blank. The domains to allow are in [Installation](https://help.usejimo.com/docs/settings/installation.md#csp-domains).

#### Chat with support

At the end of the list, **Need further help? Chat with us** opens the dashboard with a chat to the Jimo team about the tool.

When you write to us, send the experience's URL in the dashboard, the page URL on your app, and a screenshot of the tool showing the status.

## Reset user activities

The user panel holds two reset actions. Click your name at the top of the tool to open it.

| Action                       | What it does                                                                                                                                                                                                                                       |
| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Reset my user activities** | Resets all your user activities data, including experiences viewed and checklists completed, then refreshes the page. Use it to replay a flow as a new user after a first test.                                                                    |
| **Reset current experience** | Gets you out of the experience currently showing, for example when you are stuck on a step whose element is not found. That experience, and the one you are troubleshooting, can show again even if already seen, completed, dismissed or snoozed. |

<figure><img src="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FHsjhrXVALC8seJdtMshD%2Ftroubleshoot-02-user-panel-reset-actions.png?alt=media&amp;token=92fc6c95-e54f-4f07-8982-2861d032402f" alt="User panel of the Troubleshoot tool with two cards, Reset my user activities and Reset current experience, each with its Reset button"><figcaption></figcaption></figure>

To take a user out of a segment, use [Users & Segments](https://help.usejimo.com/docs/analyze/users-and-segments.md). See [Test safely](https://help.usejimo.com/docs/getting-started/publish-your-first-experience/test-safely.md).

## Verify

Open the tool on a page of your app: your name shows at the top of the tool, and the experiences you expect are listed. If you are listed as anonymous, see [Identify your users](https://help.usejimo.com/docs/getting-started/install-jimo/identify-your-users.md).

## Go further

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td><strong>Why my experience does not show</strong></td><td>Cause by cause, from the tool status to the fix.</td><td><a href="https://help.usejimo.com/docs/getting-started/publish-your-first-experience/why-my-experience-does-not-show.md">Why my experience does not show</a></td><td><a href="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FPt2g9eOv7NR2Rh7mC7u1%2FE2-c09-troubleshoot.png?alt=media&amp;token=214a280d-2970-418d-9539-0b27f183c718">E2-c09-troubleshoot.png</a></td></tr><tr><td><strong>Test safely</strong></td><td>Publish to yourself first, then widen.</td><td><a href="https://help.usejimo.com/docs/getting-started/publish-your-first-experience/test-safely.md">Test safely</a></td><td><a href="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2FXq4ivtUAniYTF4lAunZL%2FE2-c06-environments.png?alt=media&amp;token=807cf841-7d89-4813-aa16-39923b9e3970">E2-c06-environments.png</a></td></tr><tr><td><strong>Rate limiting</strong></td><td>Why an eligible experience waits behind another.</td><td><a href="https://help.usejimo.com/docs/publish/trigger-at-the-right-time-when/rate-limiting-prevent-overwhelming-users.md">Rate limiting</a></td><td><a href="https://2794860263-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKzAcDWQbK1gKbpra7bkb%2Fuploads%2F73WuPeovZ7vIJYNBBse8%2FE2-c05-rate-display-limit.png?alt=media&amp;token=5c7599f5-18cb-4551-b3f6-3f17931a893c">E2-c05-rate-display-limit.png</a></td></tr></tbody></table>

**Next page:** [Plan and billing](https://help.usejimo.com/docs/settings/plan-and-billing.md)
