wonderful-wolf-37241
04/04/2024, 6:19 AMevent
to the console and saw the following instead of the expected well-populated NLU object:
"nlu": {
"errored": true,
"openbook_model_id": "011cad83fe331216.d208c1c3dae45987"
}
I'm using the default configuration and haven't monkeyed around with the NLU config (at least not to my knowledge).
Then I noticed that the emulator's dot had turned red, which the docs state "indicates that the bot could not be trained and has some errors," but does not specify how to troubleshoot.
There were no other errors in the console apart from the NLU-related error I mentioned earlier.
It is not clear to me whether the NLU error and the emulator error are directly related, though it would stand to reason that they may be.
I already tried rolling back all the code changes that immediately preceded the NLU error, but that did not solve the problem.
All guidance, advice, and / or suggestions on how to troubleshoot these possibly-related issues will be much appreciated!wonderful-wolf-37241
04/04/2024, 3:53 PMnlu
object , and refreshing, but the emulator remained in the error state, which makes me think that maybe the NLU issue and the emulator state are not the same problemwonderful-wolf-37241
04/04/2024, 8:08 PMevent.nlu
to the console, the NLU object appeared as expectedwonderful-wolf-37241
04/04/2024, 8:10 PM