### Answer Global nodes can be transitioned to from anywhere in the call when their condition is met. [(1) ]() If your global node is being triggered repeatedly without the condition being fulfilled, here are some things to check: 1. Review your transition condition You need to set a condition for when the global node should be transitioned to. Ensure the condition precisely matches your intended trigger. Consider prompt engineering or breaking down complex conditions into multiple simpler ones. , [(2) ]() 2. Add transition finetune examples Provide examples to help the model understand your expectations for when the global node should activate. 3. Make the condition more specific If the condition is too broad (e.g.,

When user indicates this is not a good time to talk

) , the agent may interpret various user statements as matching that condition. [(1) ]() 4. Check for conflicting transitions Since global nodes can be transitioned to from anywhere, ensure other nodes don't have overlapping or ambiguous conditions that could cause repeated transitions. To debug, you can test in the dashboard (both audio and text) and see what node is highlighted to find the current node and observe how and when transitions happen. [(3) ]() If you'd like more specific help, sharing your global node's condition and the conversation flow ID would be useful.

​ To learn more, see the sources I considered: [[1] Global Node](https://docs.retellai.com/build/conversation-flow/global-node) [[2] Debug guide](https://docs.retellai.com/build/conversation-flow/debug-guide) [[3] Step 3: Add transition conditions](https://docs.retellai.com/build/conversation-flow/transition-condition) ​

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

the global node was correctly transferred to, but tehn when it left, the following node (a tool call) sent it back repeatedly without the user saying anythiing.