plain-purple•2mo ago
Conversation ending in component
I've created a component that gets reused across a couple of places. At first everything was working correctly - the mainworkflow called into the component, and the component called back into the mainworkflow when finished.
But now for some reason the conversation ends in the last block of the component, with the message saying "path not connected". I thought that when the path is not connected, the flow is handed back to the main workflow by default.
Any idea why this might be happening, or how I can work around the issue?


2 Replies
When you call a Component from the main workflow Voiceflow will only “jump back” to the main workflow through an Exit port on the Component step.
What “path not connected” means
• Runtime reached the end of the component and couldn’t find:
– an Exit step to leave the component or
– a connection on the matching exit port in the parent flow.
• When that happens Voiceflow returns an end trace, so the test tool shows path not connected and the conversation stops (it’s the same behaviour as dropping into an End step). docs Why it suddenly started happening
Most of the time one of these has happened:
1. You added / renamed / deleted an Exit step inside the component – the instance of the component in the main flow gets new ports, but the old port you had wired up is now empty.
2. The last block in the component is no longer connected to an Exit step (a branch was removed, a “No Reply/No Match” path left dangling, etc.).
3. You replaced the final Exit with an End step by mistake – an End step always terminates the whole conversation. How to fix / work-around
1. Open the component and make sure every route that should return to the parent flow is connected to an Exit step (Logic → Exit).
2. Go back to the main workflow, click the Component step and connect each exit port to the next block you want to run. If you added new exits you will see extra ports that need wiring.
3. Republish → test – the interaction should now leave the component and continue as before. Tip: If you intentionally want the conversation to finish inside the component use an End step instead of leaving a path open; this makes the intent clear and avoids the “path not connected” error message. That should get the conversation flowing again, but let me know if you’re still seeing the stop trace!
• Runtime reached the end of the component and couldn’t find:
– an Exit step to leave the component or
– a connection on the matching exit port in the parent flow.
• When that happens Voiceflow returns an end trace, so the test tool shows path not connected and the conversation stops (it’s the same behaviour as dropping into an End step). docs Why it suddenly started happening
Most of the time one of these has happened:
1. You added / renamed / deleted an Exit step inside the component – the instance of the component in the main flow gets new ports, but the old port you had wired up is now empty.
2. The last block in the component is no longer connected to an Exit step (a branch was removed, a “No Reply/No Match” path left dangling, etc.).
3. You replaced the final Exit with an End step by mistake – an End step always terminates the whole conversation. How to fix / work-around
1. Open the component and make sure every route that should return to the parent flow is connected to an Exit step (Logic → Exit).
2. Go back to the main workflow, click the Component step and connect each exit port to the next block you want to run. If you added new exits you will see extra ports that need wiring.
3. Republish → test – the interaction should now leave the component and continue as before. Tip: If you intentionally want the conversation to finish inside the component use an End step instead of leaving a path open; this makes the intent clear and avoids the “path not connected” error message. That should get the conversation flowing again, but let me know if you’re still seeing the stop trace!
plain-purpleOP•2mo ago
What is an Exit step?