SecureDataAction fails in Architect, works fine in Test GUI

I am attaching my data action. its a salesforce data action. It works fine while I test it from Action GUI but after publishing it always goes to the failure path.

I had encountered similar problems before and with the help of @Jason_Mathison, I was able to resolve it by fixing the validation errors which are not captured via Test GUI.

This time around I had made sure we have "required" validation set and available in output response too but still the same error.

Any help?

FZLogPMTTxn-20190416124034.custom.json (3.0 KB)

Hi SajidAbbasMalek,
If everything is working in test mode, then a failure in the flow probably means that you are sending the data action a bad input. My next troubleshooting step in a situation like this is to add a play audio step to my architect flow and have it speak into the call the variables that are going to be passed into the data action. Typically one of the variables will have an unexpected value, which will point me to what I have wrong in my flow.

--Jason

I wonder if your use of "call.ani" is causing you problems as call.ani generally includes a prefix of "tel:". Typically actions will use ToPhoneNumber(Call.Ani) in order to strip out the prefix and only pass in the phone number to the action.

Thank you @Jason_Mathison. You are always helpful and have good insight of data actions.

Culprit was indeed Call.Ani but it wasn't because of tel/sip prefix.

On the contrary, Call.Ani held the value of some thing like 'anonymous.inincloud.lic'. I don't know why but to get around it, I passed the ANI value from the agent script in the InvocationData and used it with the data action. This fixed the problem of going to failure at least.

Do you know why the Ani will have a value of a URL or something?

Regards
Sajid

Hi Sajid,

I asked a coworker about this, and she was surprised by the Call.ANI value you are seeing. How exactly are you kicking off this secure flow?

--Jason

Hi Jason,

I am calling this flow from agent script. I am attaching a snapshot of secure flow invocation button action.

How did the original customer call come into your system? Was it made by a cell phone, an agent's station, etc

Call was made from a cellphone, Architect flow sent it into the testing queue where only one agent was logged in. The agent had a script to send the caller back to Secure IVR. This is where Caller.Ani had unexpected text value.

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.