Service portal guided tour fails on "Requests" menu with message "Tour ended because the next step was not found."Issue On the "Service Portal", a menu item called "Requests" was defined as shown in the below screenshot, this menu item was showing the number of tickets assigned with or created by the logged-in user. A guided tour step with call-out was placed on this "Requests" menu item, and this step was failing for certain users while playing the guided tour. ReleaseAny supported release ( Madrid, Newyork release onwards).CauseThe "Requests" is a is scripted List menu item and it shows the count of the number of tickets assigned with or created by the logged-in user..The Scripted List menu item renders 2 different types of HTML as below,When the user has some tickets with him, then following scripted menu item html code is rendered, <a role="menuitem" aria-haspopup="true" ng-if="item.scriptedItems.count > 0" href="" data-toggle="dropdown" aria-label="Requests : 48" class="ng-scope"> <!-- ngIf: ::item.glyph --> <span ng-bind-html="::item.label" class="ng-binding">Requests</span> <!-- ngIf: ::!item.scriptedItems.omitBadge --> <span ng-if="::!item.scriptedItems.omitBadge" class="label label-as-badge label-primary sp-navbar-badge-count ng-binding ng-scope">48</span><!-- end ngIf: ::!item.scriptedItems.omitBadge --> </a> When the user don't have any tickets with him, then following simple html code is rendered, <a role="menuitem" ng-if="item.scriptedItems.count == 0 && item.scriptedItems.alwaysshow" ng-href="?id=requests" ng-click="collapse()" target="" title="" class="ng-scope" href="?id=requests"> <!-- ngIf: ::item.glyph --> <span ng-bind-html="::item.label" class="ng-binding">Requests</span> </a> When the guided tour was designed, if the user who is designing it, if he had tickets assigned to him or created by him, then first part of above HTML code would be rendered, then in that case, if the call-out was placed on "Requests" menu item, it will be saved with the context of that HTML available.After that, when the user who don't have any tickets with him, launches the same tour, system at same step will be looking for the original HTML, but this user will not have that same HTML, thus the step will break as it couldn't find the same HTML context.Resolution As part of product enhancement, in the latest releases(Madrid onwards), we do not provide a scripted list menu item, instead, we provide a simple page type menu item with URL to the page. Hence, this reported issue doesn't occur on the latest Madrid, Newyork releases.In order to work around the issue, please change the "Requests" menu item type from "Scripted List" to "Page" and set the page = requests.