Top
Troubleshoot Beacons using Whatfix Diagnostics
  • 10 Mar 2025
  • 4 Minutes To Read
  • Dark
    Light
  • PDF

Troubleshoot Beacons using Whatfix Diagnostics

  • Dark
    Light
  • PDF

Article summary

Note:

Whatfix Diagnostics is a Beta feature. To enable this, contact support@whatfix.com.

Consider that you have created a Beacon on your application. When you preview the Beacon, it doesn’t appear 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 Beacons, understand why they aren’t working, and follow actionable insights to resolve them.

Use the following steps to access the Whatfix Diagnostics panel:

  1. Go to the page where you want to troubleshoot your content and launch Studio.

  2. Click Preview Mode.

  3. Click Enter and then refresh the browser.


    Note:
    If the content you want to preview is in the Draft stage, then select the Include Draft content and widgets. checkbox.
  4. 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 across your application. When testing this content on different pages, you 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, the Diagnostics panel 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 content and widgets that doesn’t appear on the current page. This can 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.

  1. Expand the Beacons accordion and click Diagnose on the Beacon segment you want to troubleshoot.

    Info:

    Whatfix evaluates Beacon widgets on the page and displays the status as Evaluated or Not Evaluated.

  2. Click the Beacons section to view all the Beacons in the collection.

    Note:

    Under the Visibility Rules section, expand the accordions for Where, When Start, When End, and Who to troubleshoot any widget Visibility Rule issues.

    For more information on Advanced Visibility Rules, see Understand Advanced Visibility Rules.

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.
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 has successfully located the target element and is waiting for interaction to display the associated tooltip

Completed

Whatfix marks the step as completed, showing that the content can now be interacted with. For example, 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.

If a Beacon 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 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

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.

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.

  1. Resolve the issue using the error message.

  2. Once resolved, the status updates to Found, and the Beacon appears as intended.


Was this article helpful?

Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.