Global search not working on custom workspaceIssue When using global search on a custom workspace, no records are returned for the custom application and the search displays No results found. Selecting a quick search result redirects to the UI16 form view instead of the workspace view. The search source was configured on the Search Source [sys_search_source] table and linked to the global or workspace search application in the Search Application Configurations [m2m_search_context_config_search_source] table, but no records appear. A platform-level issue introduced in Now Platform Yokohama Patch 4 and Xanadu Patch 9 affects the search feature in customised workspaces — global search functions correctly on the global workspace, but in custom workspaces, search results are either not displayed or, when they do appear, selecting them does not open the corresponding record. This issue is fixed in Xanadu Patch 9a Hot Fix 1, Xanadu Patch 10, and Yokohama Patch 6. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } AllCause The property glide.ui.polaris.ais_ready was set to true in the instance, which caused the instance to attempt to use AI search instead of Zing. This conflict prevented search results from displaying correctly. Setting the property to false resolves the issue. Resolution 1. Verify the record exists in the instance by navigating to the sys_search_source table and checking the table directly. 2. If the record exists, confirm the search source is correctly configured in the Search Source [sys_search_source] table and linked to the appropriate search application in the Search Application Configurations [m2m_search_context_config_search_source] table. 3. Locate the system property glide.ui.polaris.ais_ready. 4. Test the search again to confirm results are returned as expected. 5. For a long-term resolution, configure the search application to use AI search as described in the ServiceNow product documentation linked in the Related Links section below. Related Links - [Configure AI search for Next Experience apps](https://www.servicenow.com/docs/bundle/zurich-platform-administration/page/administer/ai-search/concept/ais-next-experience-app.html)- [Global search not working in Agent Workspace — KB1116670](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1116670)- [Users with Business Stakeholder role not seeing Global option for search on workspace — KB2186482](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2186482)