-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dispatcher.utter_message(template=...)
no longer works in a custom action
#8223
Comments
Reported by @ArjaanBuijk and by this forum post: https://forum.rasa.com/t/dispatcher-utter-message-template-not-passing-text-attribute-to-slack-postmessage-in-rasa-2-4-0/41224 |
I'm trying to set up form bot to test the changes. |
@wochinge my question on the SDK. How are people using it now? Do they fork it and customize it? If so, I think we can include both fields and comment that if they use the older OSS version, they should use |
They either use our rasa-sdk or they write their own in their own language (as I e.g. did here. Forking and customizing the Python one over a long time period is not a thing. I mean they should ideally do the same as we will do in our Python SDK and send both the |
It does. Got it. How do I manually test the sdk? |
See here. You run rasa using |
Got the same issue on WSL Ubuntu, but it looks like a solution is on track :) |
Rasa version: 2.4.0
Rasa SDK version (if used & relevant): 2.4.0
Rasa X version (if used & relevant):
Python version:
Operating system (windows, osx, ...):
Issue:
dispatcher.utter_message(template=...)
no longer works in a custom action. Nothing is uttered by the bot. This is related to the changes introduced in #6964.Error (including full traceback):
The debug logs between Rasa 2.2 & 2.4 look the same, up to this point, after the custom action executed:
Command or request that led to error:
Content of configuration file (config.yml) (if relevant):
Content of domain file (domain.yml) (if relevant):
The text was updated successfully, but these errors were encountered: