path1 sequence action_check_intent slot{“conv_id”: “1”} inform action_check_reg slot{“regid”: “1”} inform action_check_proc slot{“procid”: “1”} inform action_check_iss slot{“issid”: “1940”} inform action_check_com slot{“comid”: “1001”} action_validate slot{“is_valid”: true} action_seq affirm OR deny utter_ack path2 posting_date action_check_intent slot{“conv_id”: “1”} inform action_check_reg slot{“regid”: “1”} inform action_check_proc slot{“procid”: “1”} inform action_check_iss slot{“issid”: “1940”} inform action_check_com slot{“comid”: “1001”} action_validate slot{“is_valid”: true} utter_file file action_post affirm OR deny utter_ack Everything runs fine apart from the fact that only path 1 gets executed irrespective of the intent . Which makes to wonder , is rasa core stories indeed full proof ? FYI i have used interactive learning to generate these stories. Any help is appreciated :slight_smile:

augmentation can be set in agent.load_data() but by saying “run rasa with --debug” did you mean run rasa_core_sdk with --debug ?? and yes i did retrain my model after interactive learning . The issue appears as i amalgamate all the stories , unlike when i keep them in different story files they seem to work just fine. thanks for the help though :slight_smile:

I meant running rasa core server with debug flag

hey will you be able to tell me how to add this in python api , since i have scripts for every task i would like to know if “–debug” can be set through python api . I am not finding a way to do so

well it depends on how you are running the server? is it flask? I would recommend using the run.py script from rasa as you will be able to take advantage of the server setup. i think if you add this by importing utils from rasa utils.configure_colored_logging(DEBUG) utils.configure_file_logging(DEBUG, logfile) maybe it could work

You say that it works fine when you seperate the stories in different files. maybe when you keep it in one story file the newline for each story might not be given so it considers as one single story. this could be problem with the editor you are using or you simply forgot to give newline at the end of a story/path. Sometimes the solution is that simple haha stories.md #story_01 *sequence - action_check_intent - slot{“conv_id”: “1”} *inform - action_check_reg - slot{“regid”: “1”} #story_02 * posting_date - action_check_intent - slot{“conv_id”: “1”} * inform - action_check_reg - slot{“regid”: “1”} Try the format you never know it might be that simple!

@stalinsabu sorry to let you know but things ain’t that simple all the time , please don’t joke around that’s totally unnecessary

I don’t think @stalinsabu is wrong though. since splitting the stories in multiple files shouldn’t really matter for training the model as all stories are concatenated together before training them. if it works putting them in two separate files and then doesn’t work upon merging, there could be something wrong on how you merge before providing data to the API. keep in mind you can also provide the folder path to the rasa API who will merge the stories together before training. how you organise your training data has no impact on how the model is trained unless you are preparing the data to train by code, you should look out for format errors

You misunderstood , by saying stories in different file, i meant in two different bots. The above 2 stories represents 2 questions asked for the bot.when i create 2 bots handling the 2 questions it works fine but as soon as i allow a single bot to handle the 2 questions by amalgamating stories , it misbehaves.So i don’t think that suggestion will work. Even i feel i might have to tune some hyperparameters.

I am sorry but i don’t think, i had a misunderstanding. having two stories file does not necessarily means you have trained two models. It wasn’t quite clear to me what you meant with two stories file. we split our stories in 10 but train one model. Maybe add a few more stories, it is a neural network you are trying to train so it will require data. You can reduce the max_history feature which by default is 5 to 3 for Memoization policy to pick up the next action which is built for precision

[SOLVED]RASA story misbehaving

Rasa Open Source

Abir (Abir) May 22, 2019, 7:00am 24

Topic		Replies	Views
Can RASA CORE follow exactly the stories defined in the stories.md file? Getting Started with Rasa rasa-stories	5	433	December 12, 2018
Rasa not following the story order Rasa Open Source	4	781	January 31, 2022
Stories are not working Rasa Open Source	5	1086	June 9, 2022
Rasa not following story Rasa Open Source	6	3027	December 12, 2018
Rasa core evaluation metrics Rasa Open Source	16	2210	July 24, 2019

[SOLVED]RASA story misbehaving

Related topics