Hi,
I have sometimes loops when a bot does not recognize any Choice to a non Skipable Question and it insists of an answer which I cannot give, because he does not understand it even if correctly written.
The end result is a loop which sometimes ends after a while when it says “You have not answered … I will go away now”
The problem is that sometimes it insists hours for the answer and it loops.
Is it any trick to reset the bot ?
I need the time to test and not wait …
Thank you,
Horia
Hi Horia,
This is actually a bug that our engineers are currently working on. It seems to have tucked itself away deep within the logic but, don’t worry our engineers will find it and fix it.
The bug that Kellsey refers to affects questions after a filter with the stop flow option ticked. The reminder shows up a little later and cannot be skipped.
I’m not sure if your problem is related. To start with the basics, you say “because he does not understand it even if correctly written” - can you give me an example of one of the choices that is not being accepted?
What happens when you type end or quit instead of answering the question?
Hi,
Thank you for the keywords end and quit. These solved the problem for the moment and are very useful. Maybe you should put them more visible for debugging users.
For the unanswerable question to disappear completely I had to disconnect the bot and recreate it, but I had my flows safe because I had two bots just in case.
Maybe this workaround would be also better to promote, as first time I pushed disconnect on my single bot I lost all my flows. Luckily this was at the beginning 
Kind regards,
Horia
I think it would be good to tell the user they can say ‘quit’ to end the interaction and stop getting the reminders.
I think @Kellsey is right about this being a bug in some cases (those where it continues for a long time). The reminder should ask a couple of times then go away.
We’ll be especially working on improving usability of our bots over the next few months. The great thing is that we’ll do that for you, so your bots will keep getting easier and easier to use without having to do anything!
Glad you got things sorted in the end. Let us know what else we can help with 
I’m also running into this bug, where it expects a ‘yes’ or ‘no’ answer but won’t accept either of them.
I tried the ‘quit’ keyword. It says that I’ve been unsubscribed, but now the bot won’t respond to any of my messages. Is there any way to re-subscribe?
–edit–
never mind, the ‘unsubscribe’ response was coming from Twilio (I was chatting over sms). looks like they are listening for the same keyword. I don’t know yet if twilio has a way to resubscribe.
Hi Yonah,
Are you still having a spot of trouble or have you managed to figure things out now?
If you need a hand figuring things out just give us a shout
Thanks @Kellsey. The unsubscribe trouble was on the twilio side. I’m still experiencing that bug with ‘confirmation’ type questions where it doesn’t accept either answer. but you guys said you’re aware and working on it 
Hi Yonah,
The bug we were working on was relating to questions being repeated when they shouldn’t have been because either they were answered or quit but this has since been fixed.
We’re not actually seeing an issue with this feature,though we think it does need to be updated. It actually accepts yes. I’ve tested it in Telegram and it’s working as it should, currently.
If you let me know what app are you using the bot with and what language are using with your bot, I’ll look into this further for you?
Thanks Kellsey. I’m using it in english with Twilio and Facebook.
I actually tried two different ways. First with question type = ‘Choice’ with ‘yes’ and ‘no’ options. Facebook works correctly, Twilio responds with “Sorry, I didn’t understand that. You can always just say ‘hello’.” and then prompts me to answer the question again.
Then I tried with question type = ‘Confirm’. Same result except this time Facebook doesn’t recognize my ‘no’ answers and responds with “I didn’t get that, can you try again?”. ‘yes’ works correctly.
Hi Yonah,
The confirm option does only accept Yes. You cannot use No. We’re actually reviewing this feature so that may very well change.
I’ll take a look at it with Twilio. Perhaps the problem lies with the Twilio integration. I’ll let you know what we find.
Hi Yonah,
I’ve tested with Twilio and all seems fine.
Would you be able to send us a screenshot of the settings for the question that you are using and your logs with the question item expanded to support@flowxo.com
I believe it may be something specific to your flow setup that is causing the problem
It seems to be working now! I’m not sure what I changed, but I’ll post back here if it happens again. Thanks for all your help!
I tried to reset with quit, end, reset, etc.
Didnt work and although I received welcome response on Messenger the flow itself would not show that it triggered.
Hmm. I think this bug still exists. I ran into it today, and tried entering “skip” around 10 times to no avail. “Quit” did work, but I didn’t know about it until coming here. Need to surface that info in the logs and bot messaging.
