Unable to publish NLU model

[Nrupada]

Unable to publish NLU model as Publish button is not visible.

[Juhi Poddar]

Hello @Nrupada 

If the Publish button is not visible when trying to publish an NLU model in ServiceNow, here are some possible reasons and solutions:

1. User Permissions: Ensure you have the necessary roles and permissions to publish NLU models. Typically, you need the nlu_admin role or specific permissions granted by your admin.

2. Model Status: Check that the model is trained and is in a "ready to publish" status. If it’s untrained or partially trained, the Publish button might not appear. Try training the model again and see if the option becomes available.

3. Browser Issue: Sometimes, browser extensions or caching issues can cause UI elements to not display correctly. Try clearing your browser cache, or open ServiceNow in a different browser or in incognito mode.

*************************************************************************************************************
"If you found my answer helpful, please give it a like and mark it as the "accepted solution". It helps others find the solution more easily and supports the community!"

Thank You
Juhi Poddar
****************************************************************************************************************

[Brian Bakker]

@Nrupada 

The versions for the NLU Model in tables [ml_solution], [sys_nlu_model_status] and [ml_capability_definition_base] will not be matching. For the Publish button to show/to enabled, the Trained version > Published version in table [sys_nlu_model_status].

This issue is usually caused by transferring the NLU Model to the target instance, and skipping the [ml_capability_definition_base] record and other records in the global scope that then causes a version mismatch on the target instance.

Please review KB0952640: NLU Model training creates a new record in table [ml_solution] for the trained NLU Model solution throwing an error and unable to publish or test, as the "Publish" button is greyed out.

Let me know if that resolved the issue.

Regards,

Brian