Hello there,
I would need some help so that Rasa does not mix similar stories. Example: imagine that I hold an apple shop and I host a chatbot in my website tha enables to buy apples and to report the rotten ones that a user may recieve. I’m using the following structure in stories.md:
## Buy apples
* intent_buy_apples
- utter_ask_for_website_user
* say_user_name{"user": "Johnny"}
- action_check_user
- slot{"valid_user" : true}
- utter_ask_for_quantity
* say_quantity{"quantity": "two"}
- action_order_items
- utter_anything_else
* say_no
- utter_goodbye
## Report rotten apples
* intent_report_issue
- utter_ask_for_website_user
* say_user_name{"user": "Johnny"}
- action_check_user
- slot{"valid_user" : true}
- utter_ask_for_issue
* say_no_of_rotten_apples{"no_of_rotten": "one"}
- action_solve_the_issue
- utter_anything_else
* say_no
- utter_goodbye
So setting aside the apple metaphor, the problem is: both stories work fine separately (considering also no-happy-paths) but the behaviour of the chatbot is confusing when both examples appear together in the same stories.md. It seems to be clear that the workflow of the chat is mixed between examples since they share “intents”, “actions” and “utters”.
Is there any option to solve this undesirable behaviour while taking advantage of shared “components”?
Many thanks in advance!