tour ended because the next step was not found

[stevekeiperSK]

Has anyone ever encountered the following scenario

setting up a guided tour with the following steps.

1 - select a record in a specific state from the list view.

2 - now on the record detail form, select an action button from the top menu

3 - highlight a state field on form and give the user some info

in this particular scenario, step 3 fails as not found.  What appears to be happening is that after the button is clicked in step 2, the form updates, and is re-rendered.  As this occurs, the info pop-up from step 3 attempts to render before the page is fully displayed, and the tour fails, because the field in question is mid-update and has not yet rendered.

there does not appear to be any way to tell the step to 'wait' and I would assume that the guided tour tool would be smart enough to allow the page to update based on the button click before moving on.  but it does not seem to do this.

Has anyone encountered this and have you been able to work around it?

[Abhay Kumar1]

@stevekeiperSK When a button is clicked (step 2), the form may reload or re-render, causing a brief period where the DOM element for step 3 (the highlighted field) is not yet available. The Guided Tour script attempts to proceed immediately, resulting in the "element not found" error because it moves faster than the page can update.

[stevekeiperSK]

Yes, this is the scenario that I have described.  If you know of any helpful advice or workaround when dealing with this timing issue, please let me know.