We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

Try NLU Model Error

gustavocami
Tera Contributor

an hour ago

Hello!

I was creating new Vocabulary Sources and Entities for one NLU Model (it's included in a Multi-lingual NLU Model set). 

After creation, I trained the model, and then when I tried to test in the NLU Workbench, the website threw an error:

Exception caught in the predict call - reason: {"status":"failure","exception":"sn_ml.MLServiceUtil.predict(): com.snc.ml.prediction.common.ServiceException: java.lang.Exception: SE0217:The solution metadata is null. Unable to retrieve: ml_x_bueu_global_global_ab2768e31b5435907c4bdd39cd4bcba9_1 [knowledge_pb.knowledge_pbCompiledFsa.json, knowledge_pb.knowledge_pb.zip, lookupSourceConfig.json]"}

gustavocami_0-1783986875982.png


I tried to Sync the Vocabulary sources again and retrain, but it didn't work.

0 Helpfuls
  • 110 Views
1 REPLY 1

Vikram Reddy
Tera Guru

57m ago

Hello @gustavocami,

 

I'm assuming the new Entity you added is backed by a vocabulary source of type Static Lookup, since that knowledge_pb bundle in the error (lookupSourceConfig.json, knowledge_pbCompiledFsa.json) is what a lookup-type fuzzy matcher solution generates, separate from the intent model itself. A Sync alone won't fix it if the underlying solution reference is stale, so before retraining again, check:

  • the Type field on the new record in sys_nlu_vocabulary, confirm it really is Static Lookup
  • the solution_name field on that record, it's likely still pointing at ml_x_bueu_global_global_ab2768e31b5435907c4bdd39cd4bcba9_1
  • whether that sys_id actually has a matching row in ml_solution, a missing or empty one is your null metadata
  • clear out solution_name on the vocabulary record, then retrain so a fresh solution gets generated instead of reusing the broken one

 

Thank you,
Vikram Karety
Octigo Solutions INC

0 Helpfuls