Data Action Failure

[Adrian_Rodriguez_Var]

Hello,
I have a problem with a data action.
I have configured it in a flow of type Workflow.
I have added notifications for the 3 branches, sucess, failure and timeout.
The data action works correctly in the UI, through the flow in 90% of the cases it goes to the failure branch, but in the performance metrics of the data action, it always executes correctly, there is no error.

On the other hand, in the failure notification it is not giving me the value of the variables configured for the execution logs.

Any idea?
BR

[Jason_Mathison]

HI BR,

I believe that the flow itself could chose to take the failure path if there is a problem with the inputs you are trying to send to the data action. This would cause the flow to take the failure path without it showing up in the performance metrics. You could try replacing each input one at a time with a hardcoded "known good" value in order to isolate the issue.

Another option is that the support department can look into why your actions are taking the failure path.

--Jason

[Adrian_Rodriguez_Var]

Hello! Thanks for answering. I have tried doing what you told me before opening the post, when I leave static values it works correctly.

Even with variables it works, but only sometimes... not always, if I execute those data actions manually they work correctly.

In the flow where I am using them, I currently use 3 data actions, is there some type of limit for workflow flows?
Thank you.
Br

[Jason_Mathison]

3 data actions in a flow shouldn't be running into any limits. I suggest working with support to figure out what the problem is.

--Jason

[Adrian_Rodriguez_Var]

What I am trying to do is to save in a variable the content of a url, that url is the one generated to get the transcript of a conversation (hosted in aws).
This is the data action itself.

{
  "name": "3.1Get Transcript Messages - RAW ",
  "integrationType": "custom-rest-actions",
  "actionType": "custom",
  "config": {
    "request": {
      "requestUrlTemplate": "${input.url}",
      "requestType": "GET",
      "headers": {
        "Password": "xxxxxxx",
        "Username": "xxxxxxx"
      },
      "requestTemplate": "${input.rawRequest}"
    },
    "response": {
      "translationMap": {},
      "translationMapDefaults": {},
      "successTemplate": "{\"raw_json\": \"$esc.jsonString(${rawResult})\"}"
    }
  },
  "contract": {
    "input": {
      "inputSchema": {
        "type": "object",
        "properties": {
          "url": {
            "type": "string"
          }
        },
        "additionalProperties": true
      }
    },
    "output": {
      "successSchema": {
        "type": "object",
        "properties": {
          "raw_json": {
            "type": "string"
          }
        },
        "additionalProperties": false
      }
    }
  },
  "secure": false
}

BR.

[Jason_Mathison]

This problem seems like something better handled by support, as they have the tools to see what is going wrong.