Rasa Slots gets None

Hi! I have two slots “save_id” and “save_name” I want these two slots to retain its value throughout the conversation

In my stories i have like this -

*ask_save_details{“save_id”:“vi.kumar”, “save_name”:“Vivek Kumar”}
-action_save_details

inside action_save_details also-
return[SlotSet(“save_id” , emp_id) , SlotSet(“save_name”, name)]

Even forcing with a return statement doesnt hold the value

when action_save_details is run , it picks the value
But as soon as other query i runs these two slots are None

Kindly help me

Hi @vi.kumar!

Just to confirm, are they getting set to None before action_restart or after?

when i check the rasa logs which come through this command -
rasa run --enable-api -m models/dialogue -m models/nlu/current --debug --endpoints endpoints.yml --cors “*”
i dnt get any log of “action_restart”

can u plz help me how to check whether action_restart is even called or not ?

Hi @vi.kumar!

action_restart should appear in your debug logs. It should look something like this:

DEBUG    rasa.core.processor  - Predicted next action 'action_restart' with confidence 

2020-07-08 00:14:43 DEBUG rasa.core.processor - Current slot values:\

    id: None
    my_id: vi.kumar
    save_id: vi.kumar

2020-07-08 00:14:43 DEBUG rasa.core.policies.memoization - Current tracker state [None, None, {}, {‘entity_save_id’: 1.0, ‘intent_ask_save_details’: 1.0, ‘prev_action_listen’: 1.0, ‘slot_save_id_0’: 1.0}, {‘entity_save_id’: 1.0, ‘intent_ask_save_details’: 1.0, ‘slot_my_id_0’: 1.0, ‘prev_action_save_details’: 1.0, ‘slot_save_id_0’: 1.0}]
2020-07-08 00:14:43 DEBUG rasa.core.policies.memoization - There is no memorised next action
2020-07-08 00:14:43 DEBUG rasa.core.policies.mapping_policy - There is no mapped action for the predicted intent, ‘ask_save_details’.
2020-07-08 00:14:43 DEBUG rasa.core.policies.two_stage_fallback - NLU confidence threshold met, confidence of fallback action set to core threshold (0.3).
2020-07-08 00:14:43 DEBUG rasa.core.policies.form_policy - There is no active form
2020-07-08 00:14:43 DEBUG rasa.core.policies.ensemble - Predicted next action using policy_1_KerasPolicy
2020-07-08 00:14:43 DEBUG rasa.core.processor - Predicted next action ‘action_listen’ with confidence 1.00.
2020-07-08 00:14:43 DEBUG rasa.core.processor - Action ‘action_listen’ ended with events ‘[]’
2020-07-08 00:14:43 DEBUG rasa.core.tracker_store - Tracker with sender_id ‘15941474813336344’ stored to database
2020-07-08 00:14:43 DEBUG rasa.core.lock_store - Deleted lock for conversation ‘15941474813336344’.
2020-07-08 00:15:19 DEBUG rasa.core.tracker_store - Can’t retrieve tracker matching sender id ‘15941475184502618’ from SQL storage. Returning None instead.
2020-07-08 00:15:19 DEBUG rasa.core.tracker_store - Tracker with sender_id ‘15941475184502618’ stored to database
2020-07-08 00:15:19 DEBUG rasa.core.processor - Received user message ‘/ask_find_open_issues_id{“id”: “vi.kumar”}’ with intent ‘{‘name’: ‘ask_find_open_issues_id’, ‘confidence’: 1.0}’ and entities ‘[{‘entity’: ‘id’, ‘start’: 24, ‘end’: 42, ‘value’: ‘vi.kumar’}]’
2020-07-08 00:15:19 DEBUG rasa.core.processor - Current slot values:
id: vi.kumar
my_id: None
save_id: None
2020-07-08 00:15:19 DEBUG rasa.core.processor - Logged UserUtterance - tracker now has 3 events\

Hlo Saurabh-m523
I have given u the logs i am getting .
U can see there are three slots {id , my_id , save_id}.
initially , my_id and save_id are filled wuth value “vi.kumar”

but afterwards ther are filled to none
U told me there must be an “action_restart” action which is running i cant see any kind of log related to this

For your information , in my actions.py file and in stories i have nowhere set my_id and save-id to None but still my slots are getting none
kindly help

Hi @vi.kumar!

I’m not an expert but I have a few suggestions for debugging this:

Here, why the sender id is changing in between conversation? What channel are you using for communication? Also based on this log, I think you are using SQL tracker store. If so, then just as an experiment, could you please try disabling the tracker store and then see if you still get the same error?

Hi saurabh
It is solved
actually the sender id was changing
thank you

1 Like