03-19-2018 02:22 AM - edited 03-14-2019 06:02 PM
On vxml we are getting some strange behave
We are getting error.badfetch on random nodes..but one thing i found it common.
in logs it shows it goes for taking the input and then throw badfetch.but that nodes we are not expecting any dtmf like they are simple audio elements or action elements.
like in the attach image getNumberLiveDetails is the action element but logs says it is requesting for dtmf input and then throw the error.
Note: We have caught error.badfetch in hotevent
03-27-2018 06:27 AM
This may seem like a basic idea, but check that the error isn't actually for the node before the one you see in the logs. We've seen instances were the logging is showing as an error for the node after where it actually happens (i.e. node 2 in the flow has the problem but the error makes it seem like it is in node 3).
03-27-2018 07:27 AM
thanks for your reply.
Yes, sometimes we also faced this issue that actual error occurs on some other node, but it seems this is not the case, as there is no audio element before and after at least till next 10 nodes.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide