- 26 Feb 2025
- 5 Minutes To Read
-
Print
-
DarkLight
-
PDF
Troubleshoot content and widgets using Whatfix Diagnostics
- Updated On 26 Feb 2025
- 5 Minutes To Read
-
Print
-
DarkLight
-
PDF
Note:
Whatfix Diagnostics is a Beta feature. To enable this, contact support@whatfix.com.
Consider that you have created a Flow on your application. When you run the Flow, some steps do not work as expected. You try to debug it but are unsure what went wrong or how to fix it. With the Whatfix Diagnostics Panel, identify issues with Flow steps, understand why they aren’t working, and follow actionable insights to resolve them.
Use the following steps to access the Whatfix Diagnostics panel:
Go to the page where you want to troubleshoot your content and launch Studio.
To enable the Whatfix Diagnostics Panel, press Option+ Shift+ D (on Mac OS) or Alt+ Shift+ D (on Windows OS) on your keyboard.
Once enabled, Whatfix Diagnostics Panel helps you view all the relevant content and widgets for that page.
Info:
Consider that you have created multiple pieces of content for a specific page in your application. When you preview the page, some content appears as expected, while others do not. This might happen due to reasons such as an incorrect URL, invalid page tag, or mismatched Visibility rules.
To help you identify what is visible and what is not, the Diagnostics panel categorizes content into two sections:
On this page: Displays 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: Displays content and widgets that are intended to appear on the current page but don’t display. This could possibly be due to a condition mismatch, such as an incorrect URL, an invalid page tag, or incorrect widget visibility rules.
These sections act as a built-in filter, helping you identify missing content and troubleshoot issues more efficiently.
Use the Search bar to find specific content or widgets.
Note:
To troubleshoot Flows, launch them through a widget such as Pop-up or Self Help.
Expand the accordion for the content you want to troubleshoot and click Diagnose.
Info:
Whatfix Diagnostics uses different statuses to describe the current state of each step or content.
Expand the accordion to understand the workflow in the Diagnostics Panel.
Understand the workflow in Whatfix Diagnostics Panel
When you enable the Diagnostics Panel, Whatfix begins evaluating the content and widgets configured for the page. It categorizes them into On this Page and Not on this page sections based on whether they match the current page conditions.
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.
Found
Whatfix locates the target element, and the step works as intended.
Displayed
Whatfix displays the content if it meets all conditions. For example, a tooltip becomes visible, or a Launcher appears.
Completed
Whatfix marks the step as completed, showing that the content can now be interacted with. For example, clicking a tooltip, completing a Flow step, or clicking a Beacon.
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.
Not Found
Whatfix does not find the target element. This happens due to reasons such as an incorrect URL or missing page tags.
Not Displayed
Whatfix finds the target element, but the content does not appear on the page. This happens due to reasons such as mismatched Visibility rules.
Note:
Whatfix evaluates Beacons, Tooltips, Launchers, and Role Tags and displays the status as Evaluated or Not Evaluated based on their conditions.
Whatfix evaluates Pop-ups, Self Help, Task List, and Surveys and displays the status as Displayed or Not Displayed based on their visibility on the page.
Whatfix searches for elements in Flow steps and tooltips and displays the status as Found or Not Found based on whether it locates the element.
If a Flow step shows the status Not found, it means Whatfix couldn’t locate the target element on the page. Clicking the status displays a Property Mismatch detected message along with an error code. For example, PROP_001 means that the properties used to identify the element have changed or can no longer be found. To troubleshoot this issue, follow the suggested resolution steps in the panel or manually reselect the element to update its properties.
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
For Flow Steps:
Status | Step status | Error Code | What does this mean? | What can you do? |
---|---|---|---|---|
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. | Reselect the target element. If the issue persists, contact support@whatfix.com. |
PROP_002 | Whatfix cannot find the target element because the HTML properties configured for the element are missing from the web page. | Reselect the target element. If the issue persists, contact support@whatfix.com. | ||
CSS selector issue detected | CSS_001 | Whatfix cannot find the target element because the CSS selector configured for the element is incorrect or missing. | Verify the added CSS selector and try again. If the issue persists, contact support@whatfix.com. | |
CSS_002 | Whatfix cannot find the target element because the auto-generated CSS selector for the element is missing | Reselect the target element. If the issue persists, contact support@whatfix.com. | ||
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. | 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. | |
Auto tag error detected | ATAG_001 | Whatfix cannot find the target element due to a failure in the Auto Tag used. | Reselect the element. If the issue persists, contact support@whatfix.com. |
For Beacons, Smart Tips, Launchers, and Role Tags:
Status | 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. |
For Pop-ups, Surveys, Self Help, and Task List:
Status | Error Message | What does this mean? | What can you do? |
---|---|---|---|
Not Displayed | Visibility rule mismatch or failure | Whatfix cannot display 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. |
Precedence issue | Whatfix cannot display the widget because another widget took priority during evaluation. | Go to the Whatfix dashboard and ensure that only one widget is live on the page. | |
Occurrence exhausted | Whatfix cannot display the widget as it has already been displayed for the set number of times. | Increase the set occurrence for the widget and try again. |
Resolve the issue using the error message.
Once resolved, the status updates to Found, and the step works as intended.