For quite a long time we have been facing a problem connected to a wrong transition between Event Handlers (“no-input-1”/“no-input-2”/“no-input-n”) OR even a missing events.
That is recurring problem that appears from time to time on different agents/flows.
#1 Example
Wrong transition between no-inputs. From “no-input-1” we went to “no-input-default” instead of “no-input-2”, that was present on the Page.
Agent structure:
- Agent starts with a “Default Start Flow”, that forwards customer to another 4 flows.
- These flows have the same construction — one by one questions with some input from a user.
Question 1: Please name the letters for Zinc (Zn);
Question 2: Please name the letter for Carbon (C);
Question n: … - On the page we have several no-input handlers (no-input-1, no-input-2, …).
- The last no-input event moves user to the “End Session” Page.
Expected Agent behaviour:
- If user is silent for the first time → GDF raises no-input-1 event
and replies with a predefined Fulfilment. - If user is silent for the second time → GDF raises no-input-2 event
and replies with a predefined Fulfilment + moves customer to the “End Session” page.
Real Agent behaviour:
- If user is silent for the first time → GDF raises no-input-1 event
and replies with a predefined Fulfilment. - If user is silent for the second time → GDF raises “no-input-default” event (instead of “no-input-2”)
and moves user to the “Start” page in the “Default Start Flow”.
#2 Example
Missed one event handler. We had two Event Handlers on a single Page: “no-input-1”, “no-input-2”.
On empty user input, “no-input-2” raised instead of “no-input-1”
Temporary solution (but sometimes it doesn’t work!)
- Go to “Agent Settings” => “ML”
- Select all flows and press “Train”
Has someone faced this issue? How can we fix it? ![]()