either I don't understand how it should work due lack of information or it literally doesn't work, but my understanding in such cases conversation should return to same spot from which conversation entered global node, right? Eg. I am in Conversational node A and I trigger condition to enter Global node (this case component), after I exit component I would like/expect to return to the Conversational node A Any feedback? https://cdn.discordapp.com/attachments/1469335707335135252/1469335707708424335/image.png?ex=69874903&is=6985f783&hm=9b75733112c6e079257c66ddf9bb5139dd50652ac92b97fbe11c917a7743270c&

I can help! You're right about how it should work after exiting a global node/component, the conversation should return to where it came from. The issue is likely that your "Go Back Condition" isn't properly configured. I can see the toggle is enabled, but the condition itself needs to be set up to know when to return to the previous node. Quick question: What condition are you using in your "Go Back Condition" section to trigger the return to the original node?

yes "Go back to previous node", its component node, that has many nodes to handle appt booking, once done it should exit component. But exit should be back to main flow to where it left it. Hope that make sense

Hello @Q4 , yes its should go back to previous node, is this not the case with you ? can you share a call id that have this issue ?

Got it! I can definitely help you set this up properly. The key is making sure your component has a clear exit condition that triggers the "Go Back" functionality. You need to configure the "Go Back Condition" to recognize when the booking process is complete like when a confirmation is given or a specific variable is set. Without that condition properly defined, the component doesn't know when to send the conversation back to the main flow.

thanks man! that was my missing peace from the puzzle!