You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've recently been experimenting with the newer versions of Voxa and Dialogflow, but I'm finding that in versions of Voxa after the change from DialogFlowPlatform to GoogleAssistantPlatform, whenever I test it out in Dialogflow, the response is "Not Available" — even though it does seem to send it through to Dialogflow in the response.
In quick summary, the fulfillmentText and fulfillmentMessages when using tell in a views.json model don't seem to come through. Only a richResponse?
For example, on a simple LaunchIntent:
If I look into the diagnostic info from Dialogflow though, I do see:
"fulfillmentText": "You said unhandled huh?",
"fulfillmentMessages": [
{
"text": {
"text": [
"You said unhandled huh?"
]
}
}
],
Is this by design? Is there a new way to ensure Dialogflow also sees the messages and gets fulfillmentText and such?
Thank you for your help!
The text was updated successfully, but these errors were encountered:
patcat
changed the title
Dialogflow editor response is "
Dialogflow editor response is "Not Available" when using v.3.3.0
Sep 19, 2019
patcat
changed the title
Dialogflow editor response is "Not Available" when using v.3.3.0
Dialogflow editor response has no filfillmentText when using v.3.3.0
Sep 19, 2019
I've recently been experimenting with the newer versions of Voxa and Dialogflow, but I'm finding that in versions of Voxa after the change from
DialogFlowPlatform
toGoogleAssistantPlatform
, whenever I test it out in Dialogflow, the response is "Not Available" — even though it does seem to send it through to Dialogflow in the response.In quick summary, the
fulfillmentText
andfulfillmentMessages
when usingtell
in a views.json model don't seem to come through. Only arichResponse
?For example, on a simple LaunchIntent:
If I look into the diagnostic info from Dialogflow though, I do see:
The code I'm using is pretty simple and largely based on the hello-world example.
When the response is given via
sayp
ortextp
is seems to work though:Is this by design? Is there a new way to ensure Dialogflow also sees the messages and gets
fulfillmentText
and such?Thank you for your help!
The text was updated successfully, but these errors were encountered: