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

​ To learn more, see the sources I considered: [[1] Global Node](https://docs.retellai.com/build/conversation-flow/global-node) ​

### Answer Based on the sources, your global node likely has the Go back to previous node feature enabled [(1) ]() . This is a specific setting for global nodes that allows the conversation to return to where it left off after the global node is handled . Here's what's happening: When you enable Go back to previous node on a global node, a Go Back Condition section appears where you define when the agent should navigate back . Once your cancellation handling completes and the go-back condition is met, the agent returns to the previous node in the flow . To check or modify this behavior: 1. Select your global node in the dashboard 2. Look for the Go back to previous node toggle in the node settings 3. If enabled, review the Go Back Condition to see what triggers the return If you don't want the conversation to return to the previous node after handling cancellation, you can: - Disable the Go back to previous node feature - Add explicit transition conditions from your global node to route to a different node instead You can also use the Prevent Immediate Re-Trigger setting to pause the global node for a specified number of node steps after it has been triggered, which prevents the conversation from looping .