Troubleshoot Linked Content using Diagnostics

Consider that you have configured a Launcher to open a Flow, but when previewed, the Launcher does not appear on the application as expected. Hence, you’re unable to open the attached Flow.

Previously, if a Launcher did not appear or failed to open its attached content, you had to return to the dashboard to check and troubleshoot the issue. With Diagnostics, you can now identify and resolve such issues directly within Diagnostics in Studio, without switching platforms.

Info:

Attached content refers to content that opens from another piece of content, such as a Flow opening from a Launcher. For more information on linking a Flow to a Launcher, see Create a Launcher.

Here’s how to troubleshoot such content issues:

5. In Diagnostics, click the Launchers accordion, and then click Diagnose on the Launcher segment you want to troubleshoot.

   Info:

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

   
   

6. Click the Launchers tab to view all the Launchers in the collection.
   
   

   Note:

   Under the Visibility Rules tab, click 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:

   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.
   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 when the end user interacts with the content. For example, clicking a Launcher.

   
   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.

   Note:

   If the Launcher shows the status Not found, it means Whatfix could not locate the target element on the page.

   

7. Click the Launcher to view why the content failed. You can see:

   a. An explanation of why the step couldn't be evaluated because some Visibility rule conditions were not met.

   b. A suggestion to review and update the Visibility rule conditions.

   c. The name of the Flow attached to the Launcher.

   

8. Click Visibility Rules.
   
   
   

   Note:

   Review the Visibility Rules configured in Studio and make the required edits.
   

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