Why the REST API does not respect my utterances?

Rasa Open Source
1

Hi all,

I am having a custom action, which uses this to send response:

dispatcher.utter_message(response="utter_debug_info")
dispatcher.utter_message(response="utter_something", json_message=debug)
print(f"ActionDialog(): step: {step}, signal: {signal}, current_utterance_index: {current_utterance_index}, utterance: {utterance}, intent: {intent}")

On rasa shell, I get the correct output:

DEBUG| step=1, signal=, utterance_index=-1
How can I help you?
Custom json:
{
  "step": "1",
  "signal": "",
  "current_utterance_index": 0,
  "utterance": "utter_offer_assistance",
  "intent": "greet_user_for_article"
}

However, through the REST API, I get only How can I help you?. Everything else is missing. How to fix this bug?

2

I have the exact same problem. I’m thinking that this might be because we don’t have a callback endpoint set in the endpoints.yml file. I will try this and see if it actually works.

3

Bump: I haven’t tried the idea that I mentioned yet, but I’m pretty sure it is the actual problem that we are facing. If you don’t have a callback endpoint, it is basically impossible for the Rasa server to send all of the queued events to the app that consumes the responses.

But now the question is… how do we associate an event with the conversation of a particular user?