### Answer Based on the available sources, the transition type

interrupt_go_back

appears to be related to Retell AI's conversation flow functionality for handling interruptions and returning to previous nodes [(1) ]() . When a global node or component is triggered during a conversation, the "Go back to previous node" feature allows the conversation to return to where it left off in the main flow . In your case: - previous node: xxx - This represents the node where the conversation was before the interruption occurred - new node: yyy - This represents the current node (likely a global node or component) that was triggered - transition type: interrupt_go_back - This indicates the system is tracking that it should return to the previous node (xxx) after completing the current node (yyy) For this to work properly, you need to configure the "Go Back Condition" to recognize when the process in the current node is complete . The condition should be set up to trigger when a confirmation is given or a specific variable is set, so the component knows when to send the conversation back to the main flow .

​ To learn more, see the sources I considered: [[1] "Go back to previous node" does not work on components or any other items that has no prompt in it.](https://discord.com/channels/1186424376300679209/1469335707335135252) ​

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