DialogFlow CX forgets events in detectIntent response

Question

I'm using dialogFlow cx from my frontend application with detectIntent request. In every Page I have added two events.

1. sys.no-match-1 that re-prompts user
2. sys.no-match-2 that allows user in case of next no-match to make transition to next specified page instead of re-prompting. But the behavior is that, the dialogFlow forgets after triggering no-match-1 and next time instead of triggering no-match-2 it again and again triggering no-match-1.

Is there any way to allow dialogFlow to remember the last event and start from next one in the next detectIntent request?

Answer 1

Normally sys.no-match-2 will trigger when user input does not match any of the training phrases after sys.no.match-1 triggered. Without looking into your project it is very difficult to answer why sys.no-match-2 is not triggering.So I recommend you raise a ticket with Google Cloud Support. If not, create a thread in Google’s Issue Tracker using this template. You can also STAR the issue to receive automatic updates and give it traction by referring to this link.

These are some basic steps you can follow to solve your issue:

1. Make sure that the Classification Threshold is not very low.
2. If possible, train your agent again using Advanced NLU.
3. Make sure that there is no overlapping between intents.

As a workaround you can try using parameter($session.counters.noMatchCnt = 2) and no-match-default for your requirement.

Here the sys.no-match-default event will trigger when user input does not match any of the training phrases. When the sys.no-match-default event is triggered again, it will satisfy the condition $session.counters.noMatchCnt = 2 and then it will route to the page you have given

Answer 2

By default, Dialogflow CX will trigger the next no-match event if, in the next turn conversation (same session), the agent doesn't detect any routes. Please make sure the no-match-1 transition is not filled.