On a very simple MENU step in a subflow, I get the error "please try again" when I select a legitimate digit (zero). When I single step through the script during active debug, no problem. Put it back in product and I get the error. I note that even if I set the Max Retires to Zero I will still generate that "please try again" error 3 times before selecting the Unsuccessful path? Where is this recording generate and for what reason?
Whe I run the script in production, when it gets to this particular Menu, something I have created about 1K times, it looks just excellent, properly formed and I can see no reason why it would behave this way. When the script is run, it gets to that Menu and each of the Filter digits works accept one, which just happens to be 0. When I select 0, I hear a message " please try again". I note that it has nothing to do with the "max retiries"? It is almost like the system is indicating it did not get that DTMF digit or something.
As far as the Reactive Debug, when I run the script in that mode, if runs flawlessly each time with no error!
As far as the reactive debug of a subflow script I have a standard practice for doing this. I bring the script into my SandBox Trigger and stuff the input values with a Java.Util.ArrayList that is full of those values so that the script runs as if it were being called by the main script. This always seems to work and I have made it a standard practise for all subflows: Create a debug boolelan toggle, that I can turn on or off for testing. Generally I also alwasy pass a value from the subflow as a booleanSuccess true or false, when returning to the main script, to deal with error handling.
So at the end of the day I am still wondering where this "please try again" error and message is coming from?
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.