Follow up intent for NO INPUT not firing with dialogflow
up vote
1
down vote
favorite
I have a "book reading" action and I tried to add a follow up intent for my read intent to reprompt a user if there was no response. Following the doc https://developers.google.com/actions/assistant/reprompts - my webhook never gets called.
However, if I add the no input handler as a main intent, I do get this event!
Is this a bug or did I miss something.
dialogflow actions-on-google
add a comment |
up vote
1
down vote
favorite
I have a "book reading" action and I tried to add a follow up intent for my read intent to reprompt a user if there was no response. Following the doc https://developers.google.com/actions/assistant/reprompts - my webhook never gets called.
However, if I add the no input handler as a main intent, I do get this event!
Is this a bug or did I miss something.
dialogflow actions-on-google
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I have a "book reading" action and I tried to add a follow up intent for my read intent to reprompt a user if there was no response. Following the doc https://developers.google.com/actions/assistant/reprompts - my webhook never gets called.
However, if I add the no input handler as a main intent, I do get this event!
Is this a bug or did I miss something.
dialogflow actions-on-google
I have a "book reading" action and I tried to add a follow up intent for my read intent to reprompt a user if there was no response. Following the doc https://developers.google.com/actions/assistant/reprompts - my webhook never gets called.
However, if I add the no input handler as a main intent, I do get this event!
Is this a bug or did I miss something.
dialogflow actions-on-google
dialogflow actions-on-google
asked 17 hours ago
Micromuncher
433113
433113
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
3
down vote
accepted
The no-input event is a little unusual, since it is handled differently internally compared to many other events. It would not surprise me if this difference requires it to be handled as a top-level Intent. You may also wish to just try setting the context in your book reading portion and having this as an input context for your no-input event.
However... this will also likely not do what you want it to do.
The no-input event will automatically terminate the conversation after three sequential events, even if you don't explicitly close the conversation.
The current way to handle this would be to use a Media Response after each portion you read. This would include a very short audio file. After the audio plays, your Action will be actions_intent_MEDIA_STATUS
event, which you can use to trigger the next portion to be read.
The exciting part is that my narrator uses SSML magic to narrate. So, if I understand what you are saying, I should play a soft "bing" (like some audio books) to denote that I'm moving on to the next page. (Thanks - that was actually really useful.)
– Micromuncher
8 hours ago
A soft "bing" or just a very short, empty, audio. Whatever works in your environment. Glad it helps!
– Prisoner
8 hours ago
add a comment |
up vote
2
down vote
No Input will be main intent as it can be reused by other intents. You may need to save bots response in a parameter in the context to check what the bot replied when handling the re-prompts from this generic No Input intent.
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
The no-input event is a little unusual, since it is handled differently internally compared to many other events. It would not surprise me if this difference requires it to be handled as a top-level Intent. You may also wish to just try setting the context in your book reading portion and having this as an input context for your no-input event.
However... this will also likely not do what you want it to do.
The no-input event will automatically terminate the conversation after three sequential events, even if you don't explicitly close the conversation.
The current way to handle this would be to use a Media Response after each portion you read. This would include a very short audio file. After the audio plays, your Action will be actions_intent_MEDIA_STATUS
event, which you can use to trigger the next portion to be read.
The exciting part is that my narrator uses SSML magic to narrate. So, if I understand what you are saying, I should play a soft "bing" (like some audio books) to denote that I'm moving on to the next page. (Thanks - that was actually really useful.)
– Micromuncher
8 hours ago
A soft "bing" or just a very short, empty, audio. Whatever works in your environment. Glad it helps!
– Prisoner
8 hours ago
add a comment |
up vote
3
down vote
accepted
The no-input event is a little unusual, since it is handled differently internally compared to many other events. It would not surprise me if this difference requires it to be handled as a top-level Intent. You may also wish to just try setting the context in your book reading portion and having this as an input context for your no-input event.
However... this will also likely not do what you want it to do.
The no-input event will automatically terminate the conversation after three sequential events, even if you don't explicitly close the conversation.
The current way to handle this would be to use a Media Response after each portion you read. This would include a very short audio file. After the audio plays, your Action will be actions_intent_MEDIA_STATUS
event, which you can use to trigger the next portion to be read.
The exciting part is that my narrator uses SSML magic to narrate. So, if I understand what you are saying, I should play a soft "bing" (like some audio books) to denote that I'm moving on to the next page. (Thanks - that was actually really useful.)
– Micromuncher
8 hours ago
A soft "bing" or just a very short, empty, audio. Whatever works in your environment. Glad it helps!
– Prisoner
8 hours ago
add a comment |
up vote
3
down vote
accepted
up vote
3
down vote
accepted
The no-input event is a little unusual, since it is handled differently internally compared to many other events. It would not surprise me if this difference requires it to be handled as a top-level Intent. You may also wish to just try setting the context in your book reading portion and having this as an input context for your no-input event.
However... this will also likely not do what you want it to do.
The no-input event will automatically terminate the conversation after three sequential events, even if you don't explicitly close the conversation.
The current way to handle this would be to use a Media Response after each portion you read. This would include a very short audio file. After the audio plays, your Action will be actions_intent_MEDIA_STATUS
event, which you can use to trigger the next portion to be read.
The no-input event is a little unusual, since it is handled differently internally compared to many other events. It would not surprise me if this difference requires it to be handled as a top-level Intent. You may also wish to just try setting the context in your book reading portion and having this as an input context for your no-input event.
However... this will also likely not do what you want it to do.
The no-input event will automatically terminate the conversation after three sequential events, even if you don't explicitly close the conversation.
The current way to handle this would be to use a Media Response after each portion you read. This would include a very short audio file. After the audio plays, your Action will be actions_intent_MEDIA_STATUS
event, which you can use to trigger the next portion to be read.
answered 12 hours ago
Prisoner
29.5k12551
29.5k12551
The exciting part is that my narrator uses SSML magic to narrate. So, if I understand what you are saying, I should play a soft "bing" (like some audio books) to denote that I'm moving on to the next page. (Thanks - that was actually really useful.)
– Micromuncher
8 hours ago
A soft "bing" or just a very short, empty, audio. Whatever works in your environment. Glad it helps!
– Prisoner
8 hours ago
add a comment |
The exciting part is that my narrator uses SSML magic to narrate. So, if I understand what you are saying, I should play a soft "bing" (like some audio books) to denote that I'm moving on to the next page. (Thanks - that was actually really useful.)
– Micromuncher
8 hours ago
A soft "bing" or just a very short, empty, audio. Whatever works in your environment. Glad it helps!
– Prisoner
8 hours ago
The exciting part is that my narrator uses SSML magic to narrate. So, if I understand what you are saying, I should play a soft "bing" (like some audio books) to denote that I'm moving on to the next page. (Thanks - that was actually really useful.)
– Micromuncher
8 hours ago
The exciting part is that my narrator uses SSML magic to narrate. So, if I understand what you are saying, I should play a soft "bing" (like some audio books) to denote that I'm moving on to the next page. (Thanks - that was actually really useful.)
– Micromuncher
8 hours ago
A soft "bing" or just a very short, empty, audio. Whatever works in your environment. Glad it helps!
– Prisoner
8 hours ago
A soft "bing" or just a very short, empty, audio. Whatever works in your environment. Glad it helps!
– Prisoner
8 hours ago
add a comment |
up vote
2
down vote
No Input will be main intent as it can be reused by other intents. You may need to save bots response in a parameter in the context to check what the bot replied when handling the re-prompts from this generic No Input intent.
add a comment |
up vote
2
down vote
No Input will be main intent as it can be reused by other intents. You may need to save bots response in a parameter in the context to check what the bot replied when handling the re-prompts from this generic No Input intent.
add a comment |
up vote
2
down vote
up vote
2
down vote
No Input will be main intent as it can be reused by other intents. You may need to save bots response in a parameter in the context to check what the bot replied when handling the re-prompts from this generic No Input intent.
No Input will be main intent as it can be reused by other intents. You may need to save bots response in a parameter in the context to check what the bot replied when handling the re-prompts from this generic No Input intent.
answered 14 hours ago
Abhinav Tyagi
3,01212035
3,01212035
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53369796%2ffollow-up-intent-for-no-input-not-firing-with-dialogflow%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown