Troubleshoot content when Whatfix Studio is not available

Consider that you’ve created content and published it, but it’s not appearing as expected for one of your end users. To identify the issue, you want to test the content directly on the end user’s browser. However, your end user’s browser does not have the Studio extension installed. In such cases, Diagnostics can still be used to identify and troubleshoot content by opening it as a standalone entity directly on the end user’s browser.

To open Diagnostics on a browser where the Studio extension is not available, follow these steps:

1. Go to the user’s browser where you want to troubleshoot the content.

2. Launch Diagnostics using the following keyboard shortcuts:

• macOS: Press Option + Shift + D

• Windows: Press Alt + Shift + D

Note:

The same steps can also be used to open Diagnostics when the Player extension is enabled on your browser.

The following GIF illustrates Diagnostics as a standalone entity on Whatfix Studio:

Once Diagnostics opens, it displays all relevant content and widgets for the page. Follow the steps mentioned in the following articles to troubleshoot your content and widgets.

• Troubleshoot Flows

• Troubleshoot Pop-ups

• Troubleshoot Beacons

• Troubleshoot Surveys

• Troubleshoot Smart Tips

• Troubleshoot Launchers

• Troubleshoot Task Lists

• Troubleshoot Self Help

• Troubleshoot Visibility Rules at the step level

• Troubleshoot Linked Content