I am testing proxy APIs for my smoke test. I have created a Flow module that verifies 200 ok status and returns the JSON response. then I have used the same flow module inside an action which sends the same output to response block of action.
Issue - When the same action is deployed and run I get below error -
{
"runId": "42a629e72d202dc0d8b61854e15df97f",
“status”: “error”,
“message”: “The response block was not set correctly.”,
Glad to hear it’s working now. We had a bug that was causing issues with modules running in deployed actions which we fixed, so everything should work now going forward.
I’m facing the same issue. I’m trying to run a flow that I’ve deployed but it doesn’t run when calling the endpoint but when I try testing it using the manual run on post man it does
I get the same error
“message”: “The response block was not set correctly.”,
Are you running this flow with the exact same scenario and payload when invoking it via API?
Also in your screenshot you’re running it locally if you press the up arrow icon next to the run button and theres a cloud run slider you can check. If your APIs aren’t reachable by our cloud environment (due to being private / behind VPN etc.) then your “Try” block will fail and you can end up with this error.
Can you check the analytics tab for when you call the flow url and see what your Try block is showing? Docs on that are here
I suspect something is going wrong in your Try flow when it’s being run in the cloud and that’s causing it to not reach the response block. Some common issues are if you have http request blocks in that flow that rely on environment variables that aren’t synced to the cloud or you’re trying to update an environment variable that you need from a pre/post request script.
