benos

I also have the issue. The entire session_config seems to be ignored. I doubt that it is related to the connector since it seems to get baked into the model...

I'm wondering if this file has anything to do with it: https://github.com/RasaHQ/rasa/blob/e9e99c31fabaa04e9f93942cec93abc33bde5218/rasa/graph_components/providers/domain_for_core_training_provider.py

Note that if I hack the metadata.json in the trained model then things behave as expected.

Thanks @dgradwell-ams That indeed sounds better than changing the metadata each time ... Is this something you can do via the Dockerfile / docker-compose or do you have to modify...

Thanks so much for the details @dgradwell-ams. As it happens I'm also dealing with local dev on the M1, but have opted to do that outside of Docker. So I...

You're probably right, but the overhead of figuring out how to create a Docker image that will work on the M1 is a bit much for me now. You can...

@wochinge @erohmensing Sorry to @ you in this way, but is the rasa team aware of this issue? It is a nasty bug that will unexpectedly bite anyone relying on...

Hi @ancalita A bit late to the party, but I tested with a fresh rasa init (works fine) and then splitting a single response into a separate file (config gets...

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...

Hi @ancalita , I've attached a demo of the issue, which is a minor modification of the "rasa init" output. [rasa_session_bug.tar.gz](https://github.com/RasaHQ/rasa/files/9297836/rasa_session_bug.tar.gz) - If you inspect the model you can see...