Maybe it is due to a underlying mechansim which I did not see. I use core 10.4 with tensorflow emebeding (13.3). I customize the intent for a specific condition if it has intent
None and is just one word in the parse function of model.py of NLU. But it seems that the fallback policy doesn not notice anything about this change? Although in Debug mode it says that it received the message with intent as I wanted and the tracker is also updated with this new intent. Why is therefore the fallback policy triggered?
When and where exatcly is the fallback triggered with intent