Not everything will work the first time that it's set up, or sometimes something will be working and then something will suddenly go wrong!
There are a few Appcues tools that can be used to get things running properly, this pro tip will get you pointed in the right direction.

Here are a few issues that might come up:
An experience isn't showing
There are issues showing in the Issues Reporting section of Flow Analytics
Need help with something else? Reach out to support at [email protected]!

An experience isn't showing

1. Make sure that Appcues is installed in the target location and make sure that there aren't any errors.
   The Installation Testing/Debugging doc covers this in detail. The basic steps are: with the builder closed, make sure the debugger opens, check for any red warnings.
2. Check the trigger to make sure that the trigger is occurring.
   Here's an example for a flow:
   
   A few quick things to check for: is the trigger occurring, is there another trigger happening right after (like another qualifying page change), is the flow set to show once (and did the trigger already occur).
3. Look for any issues with Audience Rules (qualification).
   This is covered in detail in the Diagnostics Tool doc.

There are issues showing in the Issues Reporting section of Flow Analytics

1. Check the issue name in the Issues Reporting section of the flow analytics.
   Hovering over the issue name will provide the full name and in some cases, this is enough context to know the cause of the issue. Common examples are 'could not find element for selector' or 'found multiple elements'. The Issues Reporting doc will help for context as you're investigating.
2. For additional context on the issue export the flow history. With this, we recommend doing a full export.
   
   
3. Using the export, check the activity of the users experiencing the issue to confirm the context of the issue.
   Did the issue occur on a page where the element should be valid?
   Was there unexpected behavior from the user that may have caused the issue?
   Are there any conditions or properties that are different between the users that are experiencing this issue and the ones that are not experiencing the issue?
4. Now that the investigation is done it's good to determine what to do about the issues:
   Is the issue expected and should it be ignored?
   Is there something obvious that should be fixed about the issue, should be flow targeting or selector be changed for the flow or step?
   Is the issue unexpected or unclear, if so reach out to support!