I have some issues from my Agent. It often happens that what the “user says” fall into the wrong intent. So I am trying to training the agent by the specific section “TRAINING” (please see the screenshot). I am changing the wrong intent to fix the issue and when I click on the APPROVE button then nothing happens! The problem is that training does not start (the wheel gear does not turn). And the wrong intent returns again. So the Agent continues to choose wrong intent in some cases. I would know why this training section not is working …
Related
We have an language learning Action, where the user can ask say anything they want. When they say "dinner", our Action immediately quits, without saying the cancel response.
We tried several other Actions and they all behave the same way.
Except Google Translate that says "Something went wrong".
Is there a way for our Action to react on "dinner" somehow?
I think you should make another intent where you can mention "dinner" as a training phrase. Then you can give a response against that training phrase. This might solve your problem.
I created a very simple agent on dialogflow. Every now and then, even using static responses (where only the session ID changes), the application crashes (both on Google Assistant and in the simulator).
On the logs I find the message in question: "MalformedResponse at expected_inputs [0]: Responses must provide at least one possible if this is not the final response. What does it mean?".
I don't understand what it means.
Could anyone help me?
I'm having the same problem. That i've noted is that this problem doesn't ocurre every time. The behavior is really unstable.
I'm using 2 required parameters in the intent. I don't know if that has something to do with the problem.
MalformedResponse at expected_inputs[0].input_prompt: 'input_prompt' is empty
MalformedResponse at expected_inputs[0]: Responses must provide at least one possible intent if this is not the final response
The problem, appears to be caused when you use own parameters, not when use sys. parameters.
Google answer me the following:
"Hi Alberto,
This issue has already been escalated to our engineering team. You are correct about required parameters causing the problem. Our engineering team is working thoroughly to resolve this since it is affecting some other AoG projects as well. "
I was facing the exact same issue when I was using custom entities as input parameters to my action.
I was asking for 2 custom parameters and one system (sys.color) and triggering the same with input prompts.
I found a workaround for that by taking all 3 in separate intents and using the response of the previous intent as a trigger to enter the next parameter, also by making the training phrases as sample values of the custom parameter.
I am still in contact with Dialogflow Suppport and waiting for bug fix but it works for now.
Please excuse me if this is a really basic question - I'm very much still learning, and I just cannot find a solution.
I'm trying to use the standard basic text responses in Dialogflow, which from what I understand, should work.
What I want to do, is have a set statement (Okay, let's see what I can find), then a random pick from a list, then another set statement, essentially stacking the responses in Dialogflow (see screenshot).
It works absolutely fine in Dialogflow's test console - however, it doesn't do what I want when I take it into the Google action simulator.
Have I made a stupid error, missed a toggle switch somewhere, or am I trying to do something unsupported?
To surface text responses defined in Dialogflow's default response tab go to the Google Assistant response tab and turn on the switch that says "Use response from the DEFAULT tab as the first response.":
My training page is filled with GOOGLE_ASSISTANT_WELCOME for every row. Is this normal? The agent works fine actually, just the training page is hard discern with every rows having the same name.
Sorry can't post image yet, so only can provide links to the screenshot
Page fill with GOOGLE_ASSISTANT_WELCOME screenshot
https://i.stack.imgur.com/AhhVa.jpg
GOOGLE_ASSISTANT_WELCOME with no intent invoked screenshot
https://i.stack.imgur.com/QQV3L.jpg
Yes. It is normal in the training tab in Dialogflow. It depend on how your app is invoked.
Recently we started to observer problem with Dialogflow: We have an agent with ~200 intents. Everything works as expected, but then, all of the sudden, without changing anything in the agent, intent that was matching with some input, just stops matching with the exact same input. The only way to fix it is to go and manually click train and then it works again.
Any thoughts or does anyone had the same issue?