Trying to refactor our inbound call flows to use a shared Common Module for authentication logic instead of duplicating the same set of blocks across five different queues. The goal is to have the inbound flow call the common flow, handle the auth check, and then return to the original flow based on the result.
I’ve set up the Common Module with a standard entry point and an exit point that returns a boolean flag via the Return action. In the main inbound flow, I’m using the Call Flow action to invoke this common module. I’m passing the required parameters in the input JSON.
The issue is that when the call hits the Call Flow action, it immediately fails with a 500 Internal Server Error. The debug trace shows the request leaving the main flow but never actually entering the common module’s start block. The error message in the Architect UI is just “Flow execution failed” which isn’t very helpful.
Here is the input JSON I’m passing to the Call Flow action:
{
"flowId": "9f8e7d6c-5b4a-3210-9876-543210fedcba",
"parameters": {
"authRequired": true,
"userId": "{{ participant.data.userId }}"
}
}
I’ve double-checked the flowId and it matches the common module’s ID exactly. The common module works fine when tested in isolation using the flow tester. I’ve also verified that the parameters defined in the common module match the keys in the JSON payload. The userId variable is definitely populated because I can see it in the debug log right before the Call Flow action.
Is there a specific permission issue or a known limitation with calling common modules from inbound flows? I can’t find any documentation on this specific error pattern. The flow status is active for both the main flow and the common module. I’ve tried restarting the flow but that didn’t change anything. The error happens instantly, so it’s not a timeout issue.