Hi, In some cases, the actions server might throw an exception, which causes the conversation to stuck, and it returns empty result on any input. Nothing but restarting the service (rasa, not actions) solves the issue. Not even restarting the conversation (by calling the tracker/event API): { ‘event’: ‘restart’ }
I am sure its a bug and I can’t find a solution. Thanks, Tomer.
P.S when using a DB to store the conversation, deleting the document manually form the DB solves the issue, but obviously it is very wrong.