Global Search in Custom Workspace not routing to Search Results page

[akshaynigade]

Hi all,

I’m working on a custom workspace.
The global search bar in the header is enabled (searchEnabled: true in chrome header config), but when I type a query and hit Enter, it just opens a new tab in the workspace that shows:

“Loading... The page you are looking for could not be found.”

There’s no URL change (it stays /now/workspace/{default_page_name}).

I’ve already:

Created a working Search Results page in UI Builder

Verified that the search page works when manually accessed (e.g., /search_results/97a574ea53c0130084acddeeff7b12a6/params/search-term/{value_entered_in_the_global_search}) (FYI - 97a574ea53c0130084acddeeff7b12a6 is a sysid of the globalSearchViewConfigId)

Has anyone managed to link the global search input in App Shell workspaces to a custom search results page (like /search_results)?
If so, how did you configure the route?

Thanks!

[akshaynigade · Accepted solution]

I found the root cause and it turned out to be simple.

The Workspace App Shell global search is internally routed to the /search path by default (not /search_results).

In my setup, I had created a “Search Results” page at /search_results, so when I searched from the header, the shell tried to open /search and couldn’t find it — resulting in the “The page you are looking for could not be found” error.

Fix:
I just changed my search results page route in UI Builder from /search_results → /search, published, and now the global search opens the results page correctly.