### Answer The "Go Back to Previous Node" feature in Global Nodes is documented, though there have been reported issues with its behavior. [(1) ]() How it's documented to work: Enable Go back to previous node to let the conversation return to where it left off after the global node is handled. Once enabled, a Go Back Condition section appears on the node where you define when the agent should navigate back. In the example provided, the condition is

User changed their mind and want to continue the call

. Go back conditions support both prompt-based and equation-based conditions. You can add multiple conditions and reorder them by dragging. Known issues: There have been reported problems with this feature, particularly when used with components. [(2) ]() If a global node triggers while inside a component, the go back function may return to the first node of the component instead of resuming the expected node. This has been reported to create loops in some cases. Additionally, some users have noted that Retell doesn't automatically return from global nodes, and suggest building custom logic by storing the last node in a variable and routing back manually with a Logic Split. [(3) ]() If you're experiencing specific issues with the go back functionality, I recommend checking whether you're using components in your flow, as this appears to be a known edge case. [(2) ]()

​ To learn more, see the sources I considered: [[1] Global Node](https://docs.retellai.com/build/conversation-flow/global-node) [[2] Global go back to previous node](https://discord.com/channels/1186424376300679209/1469752880369238048) [[3] fallback to the previous node from Global node](https://discord.com/channels/1186424376300679209/1388025209533235261) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.