https://discord.gg/botpress logo
Join Discord
Powered by
Troubleshooting NLU error when emulator status is ...
# 🤝help
w
Hey yall! This afternoon, I started getting an errored NLU object, similar to what I encountered last month (detailed here https://discord.com/channels/1108396290624213082/1225328937450606612/1225328937450606612) However unlike in that case, the emulator is showing status green / OK. I tried wiping out some of the more populous intents in the library, but this had no effect -- 
event.nlu
still comes through as :
Copy code
{ errored: true,
  openbook_model_id: 'd7d89a9d906b0688.d208c1c3dae45987' }
An errored NLU means that all the intent-and-entity-based bot logic fails, which renders the bot essentially broken. If anyone has guidance on how I might troubleshoot an errored NLU, I'll greatly appreciate it!
I had hoped that maybe this was a temporary issue with the NLU API being down, but it is still erroring as of this morning.
UPDATE : I tested a completely separate, new bot that I had created under a totally separate (personal) account -- the NLU still errors (with a different model ID, but again showing 
errored:  true
. So, I now suspect this is a general issue with the NLU service.
I've been combing GH but have found scant clues about troubleshooting NLU errors. I found the repo 
https://github.com/botpress/nlu
but it's not clear to me based on the README whether this NLU is the same used in Cloud, or if it is v12-only
UPDATE: I just created another new bot on a separate account, this one returned a non-errored NLU, with 
openbook_model_id: "eadfe510c28df888.d208c1c3dae45987"
. -- so clearly the NLU isn't globally down. However, rebuilding the main bot from scratch is not practical, so I still need help understanding how to troubleshoot the NLU 
errored: true
state
for anyone following this thread, BP has acknowledged an NLU outage and indicates the incident has been resolved : https://status.botpress.com/
PreviousNext
Powered by