Msg: Your text query contained only common words or ambiguous wildcards, please refine your search..

G24
Kilo Sage

Hello.  In the "HR Agent Workspace" when we create a New Case and select a person, we are sometimes getting the following unexpected message:

 

"Your text query contained only common words or ambiguous wildcards, please refine your search and try again"

 

It looks like this:

Msg1.png

 

I saw the following knowledge article:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0647596 

But I did not see "Adam" or "Schmitt" in either of the tables mentioned.

 

What might be causing this?  Or what should I check next?  Thanks.

4 REPLIES 4

Sandeep Rajput
Tera Patron

@G24 Please follow the instructions mentioned in this support article https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0868966 and see if they help.

Hi, when i try to access KB0868966 i get this error: 

Your role does not grant you access to this article. Please use Search to find related content.

 

i am logged in 

Allan_H
Tera Contributor

Did you ever find a solution to this? We are having the same issue

I only got the error message to show up once here but not sure at what stage it happened. The message itself is generally displayed when you do a text search using search terms that are only stopwords or return too many wildcard matches). The default amount seems to be 500 indexed words (sysprop glide.ts.max_wildcard_expansion).

 

So if you search for adam like in the original question, you will actually search for a list of tokens that match the root you used and the locations of the records that have the words. So if your term is ambiguous you get too many results to use in a search. 

 

Searching for adam will look for anything with root adam so if you have many adams you will have too many results. Matches from my pdi: adam(4848), adam.mccarty(842975), adam.scott(803576), adams(4843)

Screenshot 2026-03-19 120403.png

 

You can turn on debug text index and trigger the error message. Then in the debugger session log you should be able to see what the term is that is causing the error. From there it should be easier to find the root cause and come up with a resolution. 

 

The script include used for the search by the controller for the typeahead component on that page is actually editable:

/sys_script_include.do?sys_id=687d7d8deb6f3200a9e7e26ac106fee0

 

You can see from the search method that it uses the this.TEXT_QUERY constant with value "123TEXTQUERY321" for the query as in it does a keyword search