We’re trying to consolidate our IVR logic by moving a chunk of menu handling into a Common Module. The idea is to have several inbound call flows jump to this shared module, run the logic, and then return to the original flow based on the outcome. We’ve built the Common Module with a standard entry point and an exit point, but we’re hitting a wall with the return behavior. When the Common Module completes, the call drops instead of resuming the parent flow. We’re using the standard “Run Flow” action with the flow ID pointing to the Common Module. Is there a specific way to handle the return or pass context back? We’ve tried setting a variable to track the return point, but the flow just ends. Here’s the basic setup:
{
"type": "runflow",
"settings": {
"flowId": "shared-module-id",
"variables": {
"returnFlow": "${parentFlowId}"
}
}
}
The call goes into the shared module, executes, and then the conversation terminates. We need it to jump back to the original flow. Any pointers on how to structure this or if we’re missing a config step?