Solution for Virtual Agent (VA) keyword being a stop word does not work for topics and throws "Your text query contained only common words or ambiguous wildcards, please refine your search and try again" errorDescription<!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Symptoms Virtual agent topic has a keyword that is a stop word in ts_stop table and using it triggers the following error on the platform: "Your text query contained only common words or ambiguous wildcards, please refine your search and try again" error Release ALL Cause If the keyword is a stop word in ts_stop table, the topic wont show up as VA does a contextual search similar to global search and does not query stop words. Resolution Create a new record in ts_index_stop for that word in the sys_metadata and mark it as 'Not a stop word'. For example: If the keyword for a topic is issue, go to ts_index_stop and create the following record: Index: sys_metadata Word: issue Stop mode: Not a stop word