Closed cqx931 closed 2 years ago
@cqx931 I've been trying to reproduce the reported bug with rasa version 3.2.4
and so far I haven't been able to do so.
I used a rasa init
project to which I added a rule as described in the docs to enable two-stage-fallback.
After I trigger action_two_stage_fallback
, I get the expected ? Did you mean 'mood_unhappy'? 1: Yes (/mood_unhappy)
and after selecting the Yes
option, everything executes as expected, without the KeyError
.
Could you please try again with 3.2.4
and see if this behavior occurs again for you? If so, please share your example repo via a public link.
Dear @ancalita, apparently the bug occurs when there are slots declared or in use. Attached repository link that reproduces the reported bug with rasa version 3.2.4.
Rasa Open Source version 3.2.4 Rasa SDK version 3.2.0 Python version 3.8.10 What operating system are you using? Linux Link repo example: https://github.com/wise175/two_stage_fallback_test
I hope it helps to solve this bug.
Best regards
For those who can't upgrade their Rasa version because they are still testing Rasa Enterprise through RasaX:
The blogpost Handling-chatbot-failure-gracefully helped me to circumvent this issue and at the same time print out user friendly messages in the fallback 😄
Fix has just been released in version3.2.5
.
Rasa Open Source version
3.2.1
Rasa SDK version
No response
Python version
3.8
What operating system are you using?
Linux
What happened?
I'm trying to implement TwoStageFallback as described here. However, after the user clicks one of the intent options offered by the two-stage-fallback, the bot hangs by KeyError: 'action_two_stage_fallback'.
Command / Request
No response
Relevant log output