"Run Workflow" Utility fails with 400 Bad Request error

The Run Workflow utility of Developer Tools connectors seems to have an issue invoking a webhook workflow when the payload is a JSON object. The actual webhook workflow works perfectly fine when invoked from a REST Client like postman for the same input payload data.

Given below is the sample payload and the error occurred when invoking the workflow.

Payload Data:

"ErrorId": "a0",
"ErrorMessage": "Some error message",
"ErrorStackTrace": "{\"code\":404,\"name\":\"ActionUncaughtException\",\"body\":\"Error Details\"}"

Error from RunWorkflow Utlility -

<head><title>400 Bad Request</title></head>
<center><h1>400 Bad Request</h1></center>

Note: However, it works fine when the value of “ErrorStackTrace” is replaced with a regular string.

I’m not sure if this is due to a bug in the connector or some syntax issue.

Any insight is appreciated.


Note: I am using the WM.IO Integration free-forever tenant.
Tenant url - https://env499719.int-aws-us.webmethods.io/
Pl let me know if you need any additional information to help with analysis.

Hello Mir,

Explicitly passing the values in the run workflow configurations works fine for me.

But let me try out few other possibilities before we jump onto any conclusion.


As mentioned in my post, simple strings work. But a complex string like the sample payload I shared fails. Can you try it and let me know. Thanks.

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