Closed usernamedidnotfi closed 1 year ago
Exalate commented:
tttthomasssss commented:
Hey @usernamedidnotfi - thanks for raising this issue!
Could you add the contents of your domain.yml
file to this post? This will help us investigate the issue you are experiencing.
Exalate commented:
usernamedidnotfi commented:
Hey @tttthomasssss - here it is.
Thanks a lot for your help.
version: "2.0"
intents:
responses: utter_what_can_do:
actions:
slots: current_step: type: any influence_conversation: false
session_config: session_expiration_time: 0 carry_over_slots_to_new_session: true
Exalate commented:
usernamedidnotfi commented:
@tttthomasssss Hey, any updates on this? Thanks!
Exalate commented:
tttthomasssss commented:
Hey @usernamedidnotfi - the issue is in one of our engineering squads' inbox. They will estimate the effort and pick it up in one of their next rounds of issue refinement.
➤ Maxime Verger commented:
:bulb: Heads up! We're moving issues to Jira: https://rasa-open-source.atlassian.net/browse/OSS.
From now on, this Jira board is the place where you can browse (without an account) and create issues (you'll need a free Jira account for that). This GitHub issue has already been migrated to Jira and will be closed on January 9th, 2023. Do not forget to subscribe to the corresponding Jira issue!
:arrow_right: More information in the forum: https://forum.rasa.com/t/migration-of-rasa-oss-issues-to-jira/56569.
Rasa Open Source version
2.8.5
Rasa SDK version
No response
Rasa X version
No response
Python version
3.8
What operating system are you using?
Linux
What happened?
I am running Rasa in Docker, along with MySQL as a TrackerStore + custom actions. Everything seems to be working fine, but there is an issue with slots. When I try to set slot, its set just for the very moment. Whenever after that, it returns None.
The slot name is listed in domain.yml, the model is trained. Based on the records in the database, the slot value was properly set. Any chance to fix this? Of course I can save the slot values to different table (with relation to conversation_id), but thats just a temporary solution...
Command / Request
No response
Relevant log output
No response