Page 1 of 1

Error when No Input or No Match "Jump To" configured

Posted: Thu Apr 20, 2017 1:06 pm
by mka_nate
An error is occurring when the application setting for the "No Match" or "No Input" action is set to "Jump To" a page in the application. The error appears at the end of the call log as: Uncaught event: error.badfetch.http.500

To reproduce, add a menu module and set the "No Input" config to "Jump To" page 1. Call the app and just wait for the "I'm sorry, I didn't get that" prompt 3 times. Error occurs when it tries to jump to page after that 3rd no-input prompt.

Re: Error when No Input or No Match "Jump To" configured

Posted: Fri Apr 21, 2017 9:33 am
by support
This is a known bug and we're currently working on a fix. Thanks for your patience!

Re: Error when No Input or No Match "Jump To" configured

Posted: Mon May 08, 2017 3:55 pm
by support
Hello, this issue has been fixed. Please let us know if you continue to run into issues.