Global search dropdown missing in YokohamaIssue <!-- /*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: ; } } After upgrading to or running on the Yokohama release, the Global Search dropdown option is missing from the navigation interface. This symptom may occur regardless of whether the globalSearchDataConfigId UX property has been customised. 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: ; } } Yokohama Cause<!-- /*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: ; } } This issue has multiple known causes in the Yokohama release: Cause 1:The instance has the system property glide.ui.polaris.ais_ready is set to false, but the globalSearchDataConfigId UX property is configured to use AI Search settings. This mismatch causes the Global Search dropdown not to render. Cause 2 (Xanadu-to-Yokohama upgrade):Following an upgrade from Xanadu to Yokohama, the Global Search dropdown may be missing even when the globalSearchDataConfigId file is at its Out of the Box (OOB) value. This may be caused by additional upgrade-related configuration factors not covered by Cause 1. Investigation is ongoing and this article will be updated as the root cause is confirmed. Resolution<!-- /*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: ; } } Before you begin: Diagnose which cause appliesComplete the following checks before attempting any resolution steps to ensure you follow the correct path. Navigate to System Properties and search for glide.ui.polaris.ais_ready. Note its current value (true or false). Navigate to /nav_to.do?uri=sys_ux_page_property.do?sys_id=33922957c7b32010099a308dc7c26072 and review the current value of the globalSearchDataConfigId UX property. Note whether it has been customised or remains at the OOB version. Based on your findings, proceed to the applicable resolution below. Resolution 1: globalSearchDataConfigId is set to AI Search, but ais_ready is falseUse this resolution if glide.ui.polaris.ais_ready is set to false and the globalSearchDataConfigId UX property is configured to use AI Search settings. Navigate to the globalSearchDataConfigId UX property record:/nav_to.do?uri=sys_ux_page_property.do?sys_id=33922957c7b32010099a308dc7c26072 Revert the value to the appropriate OOB version using the Version History: Select Zing Search settings if your instance does not have AI Search enabled (ais_ready = false). Select the latest Out of the Box version only if AI Search is intended to be active, and ais_ready will be set to true. Save the record and clear the browser cache. Verify that the Global Search dropdown is now visible in the navigation bar. Resolution 2: Issue persists after Xanadu-to-Yokohama upgrade with unchanged configurationUse this path if the globalSearchDataConfigId is already at its OOB value and the issue appeared after upgrading from Xanadu to Yokohama. Confirm that no customisations exist on the globalSearchDataConfigId UX property record by reviewing its Version History. Check for any active update sets or customizations affecting the Global Search UX component or related UX page properties. Review the upgrade log for any errors related to UX property migration during the Xanadu-to-Yokohama upgrade. If the above steps do not resolve the issue, open a support case with Anthropic — include the results of the diagnostic checks above, your upgrade path, and any relevant update sets. Reference this article for context. Note: Resolution 2 is actively being investigated. This article will be updated with a confirmed root cause and full resolution steps as soon as they are available.