If your tour or hint shows "waiting for the target element" in the editor, it may be because of one of the following situations.
This is the most common reason for not finding the target element. Tour cards and hints use CSS selectors to find target elements in your application. When you use our editor to visually select a target, we fill in the selector for you. However, it's not always possible to find the most appropriate selector. Typical issues include:
The solution, in this case, is to add custom, unique attributes to your HTML or CSS code. This is something your developers will need to do, and we have documentation covering the topic here.
A special case is when the target element gets a different CSS class (or an attribute) when it is:
The solution, in this case, is to find an alternative selector. You can use Chrome DevTools to accomplish this.
In this case, the element is not present on the page. However, once the element appears, the step will display automatically. You don't have to change anything in this case.