> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/reports-and-analytics/analytics/funnel/troubleshoot-funnel-issues.md).

# Troubleshoot funnel issues

Fix funnel issues when a funnel is not visible, shows no data, loads slowly or does not reflect report changes, step by step.

Use this page when a funnel does not behave as expected. After following these steps, you will be able to check visibility, validate why a funnel shows no data, reduce slow load times, and verify that report changes are reflected correctly.

### Step 1: Check whether the funnel is visible

If you cannot find a funnel, check its visibility badge on the Funnel Dashboard.

A funnel set to **Only me** is only visible to the user who created it.

If needed, ask the funnel owner to change the visibility.

### Step 2: Check why the funnel shows no data

Review the configuration in this order.

1. Make sure the selected date range includes event data.
2. Make sure the funnel contains at least two steps.
3. Make sure the selected events were triggered during the selected date range.
4. Check whether audience filters or excluded events are narrowing the result too much.

For example, a new funnel can return no data if the selected date range starts before the event collection begins.

### Step 3: Reduce slow report loading

Large accounts and long date ranges can take longer to load.

Narrow the date range first.

This is especially useful when the current range is **6M** or **12M**.

### Step 4: Check why the visualization does not update

Refresh the page and open the funnel again.

The configured settings are preserved after refresh.

If the view still looks outdated, confirm that the funnel was saved after the last change.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://user.netmera.com/netmera-user-guide/reports-and-analytics/analytics/funnel/troubleshoot-funnel-issues.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.