---
title: "Troubleshoot Launchers using Diagnostics"
slug: "troubleshoot-launchers-using-whatfix-diagnostics"
tags: ["Diagnostics", "Whatfix Diagnostics"]
updated: 2025-12-02T03:24:01Z
published: 2025-12-02T03:24:01Z
canonical: "support.whatfix.com/troubleshoot-launchers-using-whatfix-diagnostics"
---

> ## 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.

# Troubleshoot Launchers using Diagnostics

> [!WARNING]
> Note:
> 
> - Whatfix Diagnostics is available across all [Delivery modes](/studio/docs/choosing-a-delivery-method).
> - If Whatfix Studio is available on the browser, open Diagnostics directly from Studio.
> - If Whatfix Studio is not available on the browser, Diagnostics can be opened as a standalone entity using **Option + Shift + D**(on macOS) or **Alt + Shift + D**(on Windows). For more information, see [Troubleshoot content when Whatfix Studio is not available](/studio/docs/troubleshoot-content-when-studio-is-not-available).

Consider that you have created a Launcher on your application. When you preview the Launcher, it doesn’t appear as expected. You try to debug it but are unsure what went wrong or how to fix it. With [Diagnostics](/studio/docs/diagnostics), identify issues with Launchers, understand why they aren’t working, and follow actionable insights to resolve them.

Use the following steps to access Diagnostics:

1. Go to the page where you want to troubleshoot your content and launch Studio. ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/CLM_editor plug in(3).png)
2. Click the **Diagnostics** icon. ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Click_Diagnostics(1).png)
3. Click **Preview Mode**. ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Click_Preview_mode(1).png)

> [!WARNING]
> Note:
> 
> If the content you want to preview is in the Draft stage, then select the **Include Draft content and widgets**. checkbox.
> 
> ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/image-1741537468606.png) If you enable **Preview Mode** from the content creation page, you must manually refresh the page to activate Preview Mode.
> 
> ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/DB_Click_preview(1).png)
4. Click **Enter** and wait for the page to refresh automatically. ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/image-1753953715382.png)

Once the page opens, Diagnostics helps you view all the relevant content and widgets for that page.

> [!NOTE]
> Info:
> 
> Consider that you have created multiple pieces of content across your application. When testing this content on different pages, you would expect it to appear on the correct page or section.
> 
> To help you identify the content that is applicable to appear on a specific page, Diagnostics categorizes content into two sections:
> 
> - **On this page**: Lists content and widgets that are configured to appear on the current page. This includes content that has a valid URL or page tag condition that matches the current page.
> - **Not on this page**: Lists contents and widgets that don't belong on the current page. This implies the visibility rules, URL conditions, or page tags that are not applicable on the current page.
> 
> The sections act as a built-in filter, helping you identify missing content and troubleshoot issues more efficiently. ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/image-1744176197051.png)
> 
> - Use the **Search** bar to find specific content or widgets.

1. Expand the **Launchers** accordion and click Diagnose on the Launcher segment you want to troubleshoot.

> [!NOTE]
> Info:
> 
> Whatfix evaluates Launcher widgets on the page and displays the status as **Evaluated** or **Not Evaluated**.

![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Launcher_WD(1).png)
2. Click the **Launchers**section to view all the Launchers in the collection. ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Launcher_Widgets_WD.png)

> [!WARNING]
> Note:
> 
> Under the**Visibility Rules** section, expand the accordions for **Where**, **When Start**, **When End**, and **Who** to troubleshoot any widget Visibility Rule issues. ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Launcher_VR.png)
> 
> For more information on New Visibility Rules, see [Understand New Visibility Rules](/studio/docs/understand-visibility-rules-20).

> [!NOTE]
> Info:
> 
> Diagnostics uses different statuses to describe the current state of each step or content.
> 
> Expand the accordion to understand the workflow in Diagnostics.
> 
> ****Understand the workflow in Diagnostics****
> 
> When you enable Diagnostics, Whatfix begins evaluating the content and widgets configured for the page. As you interact with the content, Whatfix updates the status at each step, helping you understand what is working and what is not.
> 
> **Success path: When content or step works as expected**
> 
> | Status | What does this mean? |
> | --- | --- |
> | **Searching** | Whatfix searches for the target element on the page. It tries to locate the UI component the content or step is linked to.![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Launcher_searching.png) |
> | **Found** | Whatfix has successfully located the target element and is waiting for interaction to display the associated tooltip. ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Launcher_found.png) |
> | **Completed** | Whatfix marks the step as completed, showing that the content can now be interacted with. For example, clicking a Launcher. ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Launcher_Clicked.png) |
> 
> **Not Found path: When content does not appear**
> 
> | Status | What does this mean? |
> | --- | --- |
> | **Searching** | Whatfix starts searching for the target element on the page. It tries to locate the UI component the content or step is linked to.![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Launcher_searching(1).png) |
> | **Not Found** | Whatfix does not find the target element. This happens due to reasons such as an incorrect URL or missing page tags. ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Launcher_Notfound.png) |

> [!WARNING]
> Note:
> 
> If a Launcher shows the status **Not found**, it means Whatfix does not locate the target element on the page. For example, clicking the status displays a **CSS selector issue detected** message. To troubleshoot this issue, follow the suggested resolution steps in Diagnositcs or manually reselect the element to update its properties. ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/CSS_Selector_WD.png)

Click the following accordion to view the error message, their meanings, and the steps to resolve the issue.

****Error message, their meanings, and steps to resolve them****

| Status | Step status | Error Code | Error Message | What does this mean? | What can you do? |
| --- | --- | --- | --- | --- | --- |
| **Not Evaluated** | - | - | Visibility rule mismatch or failure | Whatfix cannot evaluate the widget because some of the Visibility rule conditions aren’t met. | Review the Visibility rule conditions and make any necessary modifications. If the issue persists, contact [support@whatfix.com](mailto:support@whatfix.com?subject=Flow%20step%20error&body=Team%2C%20%0AI%20am%20getting%20a%20Not%20found%20error%20on%20the%20Flow%20step.%20Kindly%20help). |
| **Not Found** | Property mismatch detected | PROP_001 | Whatfix cannot find the target element because the unique properties used to identify it during creation have changed or are missing. | Whatfix cannot locate the element because its unique identifying properties changed or no longer exist. | Reselect the target element. If the issue persists, contact [support@whatfix.com](mailto:support@whatfix.com?subject=Flow%20step%20error&body=Team%2C%20%0AI%20am%20getting%20a%20Not%20found%20error%20on%20the%20Flow%20step.%20Kindly%20help). |
| PROP_002 | Whatfix cannot find the target element because the HTML properties configured for the element are missing from the web page. | Whatfix cannot locate the element because the required HTML properties are missing from the page | Reselect the target element. If the issue persists, contact [support@whatfix.com](mailto:support@whatfix.com?subject=Flow%20step%20error&body=Team%2C%20%0AI%20am%20getting%20a%20Not%20found%20error%20on%20the%20Flow%20step.%20Kindly%20help). |
| CSS selector issue detected | CSS_001 | Whatfix cannot find the target element because the CSS selector configured for the element is incorrect or missing. | Whatfix cannot locate the element because the specified CSS selector is incorrect or missing. | Verify the added CSS selector and try again. If the issue persists, contact [support@whatfix.com](mailto:support@whatfix.com?subject=Flow%20step%20error&body=Team%2C%20%0AI%20am%20getting%20a%20Not%20found%20error%20on%20the%20Flow%20step.%20Kindly%20help). |
| CSS_002 | Whatfix cannot find the target element because the auto-generated CSS selector for the element is missing | Whatfix cannot locate the element because the automatically generated CSS selector does not exist. | Reselect the target element. If the issue persists, contact [support@whatfix.com](mailto:support@whatfix.com?subject=Flow%20step%20error&body=Team%2C%20%0AI%20am%20getting%20a%20Not%20found%20error%20on%20the%20Flow%20step.%20Kindly%20help). |
| Search time out | ETO_001 | Whatfix cannot find the target element because the element search operation times out. The target element might not have been loaded yet or might not exist on the page. | Whatfix cannot find the element because it is not loaded on the page or does not exist, causing a timeout. | Verify that the element is on the page or perform an action to make the element appear. If the issue persists, contact [support@whatfix.com](mailto:support@whatfix.com?subject=Flow%20step%20error&body=Team%2C%20%0AI%20am%20getting%20a%20Not%20found%20error%20on%20the%20Flow%20step.%20Kindly%20help). |
| Auto tag error detected | ATAG_001 | Whatfix cannot find the target element due to a failure in the Auto Tag used. | Whatfix cannot locate the element because the Auto Tag failed to identify it. | Reselect the target element. If the issue persists, contact [support@whatfix.com](mailto:support@whatfix.com?subject=Flow%20step%20error&body=Team%2C%20%0AI%20am%20getting%20a%20Not%20found%20error%20on%20the%20Flow%20step.%20Kindly%20help). |

1. Resolve the issue using the error message.

Once resolved, the status updates to **Found**, and the Launcher appears as intended. ![](https://cdn.document360.io/a268766e-d74d-4619-9613-e2472f809ffb/Images/Documentation/Launcher_found(1).png)