AI Search Profile Not Getting Published

Rakesh50
Mega Sage

Hi, 

 

We are currently encountering an issue where the AI Search profiles we have configured are not getting published as expected. Despite following the standard configuration steps, the profiles remain in an unpublished state.

 

We are trying to get the search results with help of AI Search through script and we followed the script to get search results from the link https://www.servicenow.com/community/developer-articles/call-ai-search-using-script/ta-p/2652596.

Could you please advise if there are any specific plugins that need to be installed or if a particular subscription or license tier is required to enable this functionality?

 

Rakesh50_0-1751291747005.png

The logs we are getting as below:- 


NOW-AI_SEARCH-DICTIONARY_SYNC_ERROR: Additional information - Failed to derive AIS
dictionary knowledge_search_for_chatbot_default_spell_check_dictionary, msg:
com.attivio.module.aisapi.v20.ApiException: Conflict, response body:
{"code":409,"class":"Partition State","message":"Write API is not supported for partition
8fca5d91db4a29145dc32f17d496191a (current state: PASSIVE_ELIGIBLE)."} : Cause -
com.attivio.module.aisapi.v20.ApiException: Conflict:
com.glide.ais.error.SearchRuntimeException: NOW-AI_SEARCH-
DICTIONARY_SYNC_ERROR: Additional information - Failed to derive AIS dictionary
knowledge_search_for_chatbot_default_spell_check_dictionary, msg:
com.attivio.module.aisapi.v20.ApiException: Conflict, response body:
{"code":409,"class":"Partition State","message":"Write API is not supported for partition
8fca5d91db4a29145dc32f17d496191a (current state: PASSIVE_ELIGIBLE)."} : Cause -
com.attivio.module.aisapi.v20.ApiException: Conflict:
com.glide.ais.communication.DictionarySyncApi.deriveDictionary(DictionarySyncApi.java:53)
com.glide.ais.configuration.synchronizer.dictionary.DictionarySynchronizer.publish(DictionarySy
nchronizer.java:73)
com.glide.ais.configuration.synchronizer.profile.SearchProfileSynchronizer.publishDefaultSpellC
heckDictionary(SearchProfileSynchronizer.java:128)
com.glide.ais.configuration.synchronizer.profile.SearchProfileSynchronizer.publish(SearchProfil
eSynchronizer.java:80)
com.glide.ais.configuration.synchronizer.AisSynchronizer.publishProfile(AisSynchronizer.java:51
)
com.glide.ais.configuration.synchronizer.ScriptableAisSynchronizer.jsFunction_publishProfile(Sc
riptableAisSynchronizer.java:51)
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:77)
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:43)
java.base/java.lang.reflect.Method.invoke(Method.java:569)
org.mozilla.javascript.MemberBox.invoke(MemberBox.java:236)
org.mozilla.javascript.FunctionObject.doInvoke(FunctionObject.java:674)
org.mozilla.javascript.FunctionObject.call(FunctionObject.java:603)
org.mozilla.javascript.ScriptRuntime.doCall(ScriptRuntime.java:2988)
org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:1928)
org.mozilla.javascript.Interpreter.interpret(Interpreter.java:1112)
org.mozilla.javascript.InterpretedFunction.lambda$call$0(InterpretedFunction.java:161)
com.glide.caller.gen.sys_ui_action_90dc024553230010bca8ddeeff7b12b2
➚_script.call(Unknown Source)
com.glide.script.ScriptCaller.call(ScriptCaller.java:22)
org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:160)
org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:719)
org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:4412)
org.mozilla.javascript.InterpretedFunction.exec(InterpretedFunction.java:174)
com.glide.script.ScriptCompiler.executeAndPublishMetric(ScriptCompiler.java:77)

com.glide.script.ScriptEvaluator.execute(ScriptEvaluator.java:439)
com.glide.script.ScriptEvaluator.evaluate(ScriptEvaluator.java:219)
com.glide.script.GlideRhinoHelper.evaluateAsString(GlideRhinoHelper.java:164)
com.glide.script.ActionScript.conditionalEval(ActionScript.java:110)
com.glide.script.ActionScript.execute(ActionScript.java:95)
com.glide.script.ActionScriptProcessor.processScript(ActionScriptProcessor.java:233)
com.glide.script.Action.process(Action.java:117)
com.glide.ui.RedirectTransaction.invokeAction(RedirectTransaction.java:552)
com.glide.ui.RedirectTransaction.handleActions(RedirectTransaction.java:508)
com.glide.ui.RedirectTransaction.inboundActions(RedirectTransaction.java:344)
com.glide.ui.RedirectTransaction.process(RedirectTransaction.java:207)
com.glide.ui.GlideServletUITransaction.process(GlideServletUITransaction.java:124)
com.glide.processors.AProcessor.runProcessor(AProcessor.java:779)
com.glide.processors.AProcessor.processTransaction(AProcessor.java:326)
com.glide.processors.ProcessorRegistry.process0(ProcessorRegistry.java:187)
com.glide.processors.ProcessorRegistry.process(ProcessorRegistry.java:175)
com.glide.ui.GlideServletTransaction.process(GlideServletTransaction.java:58)
com.glide.sys.Transaction.run(Transaction.java:2803)
com.glide.ui.HTTPTransaction.run(HTTPTransaction.java:35)
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
java.base/java.lang.Thread.run(Thread.java:840)

 

5 REPLIES 5

Isaac Vicentini
Mega Sage
Mega Sage

Hi @Rakesh50,

 

Check the record in the "Typo Handling" related list.

Is it published?
Is it active?
Is it a single record?
Try unlinking and relinking it.


Best regards,

Isaac Vicentini
MVP 2025


If my answer was helpful, mark it as Helpful or Accept as Solution.

Hi @Isaac Vicentini ,

Thanks for the reply. In the Typo Handling section, we are unable to see the Link and Unlink options. However, we are able to see these options for the Search Sources related list.

Also, the Typo Handling record is not published — it is currently in draft state. We are unable to see the Publish option for this record

Rakesh50_0-1751354141199.png

These below are the logs when we executed the script(https://www.servicenow.com/community/developer-articles/call-ai-search-using-script/ta-p/2652596) in background

#68509 [ais] SearchProfileRelevancyProvider: No current published relevancy model available for profile: a4ca798ffffc21105841c9b7cddcbda7
SearchQueryService: #68509 [ais] SearchQueryService: AIS Semantic Logging - Query searchQuery=issue, searchProfile=a4ca798ffffc21105841c9b7cddcbda7, requestCount=1, geniusRequestCount=0, embeddingCount=0, userID=7467d05947aeda1089cd8311236d4325, sessionID=7BEA3910476EA21089CD8311236D4380, semanticSearchPluginEnabled=false
#68509 [ais] SearchQueryService: Sending out search request to AIS Service for search request: 11c18efb-be47-42a7-9b40-0ead3e371ee4
#68509 [ais] SearchQueryService: Received response from AIS Service for search request: 11c18efb-be47-42a7-9b40-0ead3e371ee4
*** Script: {"query":"sys_idIN","kb":[]}

 

I suggest you create this from scratch and see if that solves your issue. I did following:

 

1) Created new Search profile

2) Linked 'Search sources'

3) Once step 2 is done Typo automatically came and I simply published and it worked.

 

Reference: Publish button missing in Typo handling dictionary AI Search


Best regards,

Isaac Vicentini
MVP 2025


If my answer was helpful, mark it as Helpful or Accept as Solution.

We tried this approach, but it didn’t work and we were unable to publish the search profile. However, we connected with the HI Support team, and they informed us that the issue was related to AI Search health, which they fixed internally.

Before that, we had installed the sn_itsm_gen_ai plugin and attempted the same, but the issue still wasn’t resolved.

Do you think this plugin is necessary to publish the search profile? Do you have any insights on this?