rasa: Setting domain session_expiration_time has no effect
h3. Rasa Open Source version
3.1.0
h3. Rasa SDK version
No response
h3. Rasa X version
No response
h3. Python version
3.9
h3. What operating system are you using?
Linux
h3. What happened?
Since version 3.1.0, my preference for session_expiration_time (0) under session_config in the domain doesn’t seem to be working anymore. The value is always being set to 60, the default.
I’ve confirmed that this is the actual value in three ways,
Inspecting the result of the API call to [get the domain| https://rasa.com/docs/rasa/pages/http-api#operation/getDomain] of the running bot
Extracting the trained model archive and inspecting the merged domain therein, and
Every 60 minutes of actual inactivity on my session, action_session_start is invoked
This happens whether my domain is contained in a single file or split into multiple files in a directory. I’ve tried deleting the trained models and the .rasa cache directory and retraining the model to no avail.
Thing is, we have overridden the action_session_start in our project, and it has considerable side effects in our app that are only meant to be run once for each conversation. We cannot call it again – we don’t want sessions to expire.
h3. Command / Request
No response
h3. Relevant log output
No response
h3. Reproduction repository
[https://github.com/dgradwell-ams/rasa-issue-11061| https://github.com/dgradwell-ams/rasa-issue-11061]
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 29 (7 by maintainers)
Hi @ancalita
From the changelog of 3.2.4 I understand the problem should be fixed with that release. However I find that not to be the case; if I train with a split domain file and then inspect the metadata.json of the model it still uses the default value.
Thanks,
Ben
@rgstephens Here’s a repo that reproduces the issue https://github.com/dgradwell-ams/rasa-issue-11061
I’ve set the expiration time to 1 minute in the configuration to demonstrate easily. See the README.