Unnecessary "Guided Tours" transactions for non-Guided Tours pagesIssue After opening a record in the backend, the client browser is requesting "Guided Tour" data from the instance in a separate transaction, even when there is no guided tour defined for the current type of record. This may cause high session wait times and high response times in the log entries since the loading of the related list data has to be completed in the first place.CauseGuided tours will make a REST API call to determine if there is a tour configured for the given page, for example if the user visits home.do page, it is not known if there is any tour configured for the home.do, so a REST API call is made to determine if there are any tours.ResolutionThe call was optimized since Paris, and populates at the same time the list of guided tours and the list of auto launchable tours on the page.Related LinksAutolaunch transactions are generated even when Guided Tours Auto Launch is not enabled