---
title: "Content not showing in Explorer"
slug: "content-not-showing-in-explorer"
updated: 2026-08-13T14:31:16Z
published: 2026-08-13T14:31:16Z
canonical: "support.whatfix.com/content-not-showing-in-explorer"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.whatfix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Content not showing in Explorer

## Issue

- You have added content to your Improved Self Help segment, but it does not display in Explorer when you try to access it on the application.
- Improved Self Help content is not displayed in the Development instance.

## Probable Causes

- Content such as Flows, Videos, and Articles, may not show up in Explorer in the Production instance when the content,
  - Is not a part of any Self Help segment.
  - Does not have proper tags attached to it.
  - Is segmented to not appear to certain users based on their user roles.

Debug:

You must tag your content with a tag or combination of tags that are present on the page. To check which tags are loading on a particular page, you can use Whatfix's debugging commands in your browser's Developer Tools. For more information, click the following accordion:

**Identify tags loaded on a page**

Use the following steps to get the debug logs:

1. Go to the page in your application where you want to get the loaded Tags. ![support_site.png](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/support_site.png?sv=2026-02-06&spr=https&st=2026-11-12T09%3A03%3A39Z&se=2026-11-12T10%3A03%3A39Z&sr=c&sp=r&sig=B%2Fs5Mc6VbgPMIJ3eVgFYv2CQgArovA9Q2oqUExELcQU%3D)
2. Open your browser's **[Developer Tools](https://developer.chrome.com/docs/devtools/open).** ![support_devtools.png](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/support_devtools.png?sv=2026-02-06&spr=https&st=2026-11-12T09%3A03%3A39Z&se=2026-11-12T10%3A03%3A39Z&sr=c&sp=r&sig=B%2Fs5Mc6VbgPMIJ3eVgFYv2CQgArovA9Q2oqUExELcQU%3D)
3. Go to the **Console** tab. ![debug_console.png](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/debug_console.png?sv=2026-02-06&spr=https&st=2026-11-12T09%3A03%3A39Z&se=2026-11-12T10%3A03%3A39Z&sr=c&sp=r&sig=B%2Fs5Mc6VbgPMIJ3eVgFYv2CQgArovA9Q2oqUExELcQU%3D)
4. Type **_wfx_settings.debug_mode=true;** and press Enter. ![debug_mode.png](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/debug_mode.png?sv=2026-02-06&spr=https&st=2026-11-12T09%3A03%3A39Z&se=2026-11-12T10%3A03%3A39Z&sr=c&sp=r&sig=B%2Fs5Mc6VbgPMIJ3eVgFYv2CQgArovA9Q2oqUExELcQU%3D)

Here, you are setting the **_wfx_settings.debug_mode** variable to a **true** value, which instructs Whatfix to provide debug logs for Whatfix widgets whenever they load on a page.

1. Type **_wfx_refresh();** and press Enter.  

![wfx_refresh.png](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/wfx_refresh.png?sv=2026-02-06&spr=https&st=2026-11-12T09%3A03%3A39Z&se=2026-11-12T10%3A03%3A39Z&sr=c&sp=r&sig=B%2Fs5Mc6VbgPMIJ3eVgFYv2CQgArovA9Q2oqUExELcQU%3D)

The **_wfx_refresh();** command reloads all Whatfix content and widgets that are supposed to load on the page.

After getting the debug logs, click **IS is enabled : applying on top of base segment** to expand its output. ![debug_IS_is_enabled.png](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/debug_IS_is_enabled.png?sv=2026-02-06&spr=https&st=2026-11-12T09%3A03%3A39Z&se=2026-11-12T10%3A03%3A39Z&sr=c&sp=r&sig=B%2Fs5Mc6VbgPMIJ3eVgFYv2CQgArovA9Q2oqUExELcQU%3D)

Inside, there are objects containing the names of the Tags evaluated on that particular page. ![debug_tag_name.png](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/debug_tag_name%281%29.png?sv=2026-02-06&spr=https&st=2026-11-12T09%3A03%3A39Z&se=2026-11-12T10%3A03%3A39Z&sr=c&sp=r&sig=B%2Fs5Mc6VbgPMIJ3eVgFYv2CQgArovA9Q2oqUExELcQU%3D)

Each object contains the following information:

- **conditions**: The conditions required for that Tag to load.
- **flows**: The count of content this Tag is attached to.
- **name**: The name of the Tag.
- **type**: The type of the Tag, that is, **Page**, **Role**, or **Other** Tag.

![debug_evaluated_tag.png](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/debug_evaluated_tag.png?sv=2026-02-06&spr=https&st=2026-11-12T09%3A03%3A39Z&se=2026-11-12T10%3A03%3A39Z&sr=c&sp=r&sig=B%2Fs5Mc6VbgPMIJ3eVgFYv2CQgArovA9Q2oqUExELcQU%3D)

## Suggested Solutions

- Ensure that the content is part of a segment. Content is displayed in Explorer only if it is part of a Self Help segment.
- If you are using a role tag, ensure that all your content has at least one [role tag](/desktop/docs/create-role-and-page-tags).
- Check if the content is appropriately tagged.

> [!WARNING]
> Note:
> 
> If the issue persists, contact [support@whatfix.com](mailto:support@whatfix.com?Subject=Content%20not%20showing%20up%20in%20Explorer%20Help&Body=Hello%20Team%2C%0A%0AContent%20not%20showing%20up%20in%20Explorer.%20Kindly%20provide%20assistance.%0A%0AMore%20information%3A%20%0A%0AThanks%20and%20regards.).