> 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/getting-started/publish-your-first-experience/why-my-experience-does-not-show.md).
# Why my experience does not show
You published, you opened your app, nothing. Open the Troubleshoot tool on that page first: it lists every published experience with a status and the conditions that matched or not. Then go down this list in order.
***
## Open the Troubleshoot tool
From the experience's **...** menu in the dashboard, click **Troubleshoot** and enter the URL of your app. Or press the shortcut on any page of your app once you enabled it in [Settings > Troubleshoot](/docs/settings/troubleshooting.md). The tool shows your user, your segments, and each experience as **Shown**, **Seen**, **Waiting** or **Ineligible**, with the conditions behind the status.
If the tool itself does not open, the snippet is not running on this page: jump to cause 5.
## Settings doing what they were told
The first five are settings doing what they were told, not bugs. Go down them in order.
#### 1. You already saw it
Status **Seen**. Experiences show once per user by default. You saw it in your first test, so it will not show again. Click **Reset user activities** in the tool's user panel to clear what this browser has seen, then reload. It acts on this browser only and does not touch analytics. See [Test safely](/docs/getting-started/publish-your-first-experience/test-safely.md).
#### 2. Rate limiting held it back
Status **Waiting**, with rate limiting listed. By default a user gets at most one experience per 4 hours. If you tested another experience earlier, this one waits. Either wait, or turn rate limiting off for this experience in **When** while you test, and turn it back on before opening it to everyone. See [Rate limiting](/docs/publish/trigger-at-the-right-time-when/rate-limiting-prevent-overwhelming-users.md).
#### 3. The environment or the Where does not match
Status **Ineligible**, with "environment" or "URL" among the unmatched conditions. Three checks:
* The **Env** on the experience includes the domain you are on. "All domains" matches everything; a named environment matches only its domains, typed without scheme or path.
* The **Where** rule matches the page's path. A trailing slash on the live URL makes an `equals` rule fail; use `contains` or `starts with`. A Where rule that names a domain outside the selected environment matches nothing.
* You are on the right app: staging and production have different domains.
See [Environments and domains](/docs/getting-started/your-workspace/environments-and-domains.md).
#### 4. The audience excludes you
Status **Ineligible**, with a segment or attribute condition unmatched. The user panel at the top of the tool shows which segments you belong to and your attributes' values. Compare with the **Who** of the experience. The usual cases: the segment relies on an attribute your app does not send yet, or the "has not completed" condition is false because you completed it in a test. See [Who](/docs/publish/target-right-people-who.md).
#### 5. Jimo did not initialize on this page
The Troubleshoot tool does not open, and in the console `window.jimo` is `undefined` or `[]`. Either the snippet is not on this page (check [Settings > Installation](/docs/settings/installation.md) for detection, and whether this page is excluded by [Manual initialization](https://help.usejimo.com/docs/for-developers/for-developers/sdk-guides/manual-initialization)), or **Force Identify** is on and no identify call ran on this page. A CSP block gives the same symptom: look for "Content Security Policy" in the console. See [Install Jimo](/docs/getting-started/install-jimo.md).
## Three more causes
Once the first five are ruled out, check these.
#### 6. The trigger never fired
Status **Waiting**, with the trigger listed. The experience is eligible and waits for its Show on condition: a click on an element that is not on this page, an event your app never sent, a delay. Check the trigger in **Show on**, and for an element-based trigger, that the selector still matches ([Stable selectors](/docs/getting-started/create-your-first-experience/stable-selectors-on-a-dynamic-front-end.md)).
#### 7. Publish was never possible
Two cases that stop before publication. A step with an empty media block, or an invalid step, keeps the Publish button disabled without saying why: open each step and look for an empty image or video block. A role without the publish permission cannot publish: see [Roles and permissions](/docs/getting-started/your-workspace/roles-and-permissions.md).
#### 8. Another experience is in the way
Only one experience shows at a time. If a banner or a modal is already on screen, the next one waits. The tool shows the blocking relation on the waiting experience. Close the first one, or review the priorities between your experiences.
## Still nothing
Write to us from the chat with the experience's URL in the dashboard, the page URL on your app, and a screenshot of the Troubleshoot tool showing the status. That is everything we need.
## Related
* [Troubleshooting](/docs/settings/troubleshooting.md), the tool's reference
* [Test safely](/docs/getting-started/publish-your-first-experience/test-safely.md)
* [Target & Publish](/docs/publish/target-and-publish.md)
