I don’t have access to analyze specific call IDs directly. However, based on the looping issues documented in the sources, here are specific debugging steps for your calls:
Immediate actions to take:
-
Review your global node conditions - Check if the condition for when the global node should trigger is too broad or vague. The condition needs to be specific enough that it doesn’t accidentally match unrelated user questions.(1)
-
Check for split nodes after global nodes - If your flow has a split node immediately after a global node, this is a known issue where the else condition can loop back to the global node incorrectly.(5) The Retell team acknowledged this specific bug.(5)
-
Add transition finetune examples - For the nodes involved in the loop, add finetune examples showing when the agent should NOT transition to the global node.(7)
-
Make transition conditions more specific - Instead of general conditions, be explicit about what should trigger the transition. For example, instead of “User indicates this is not a good time to talk”, specify exact phrases or scenarios.(7)
-
Try adding a conversation node after the global node - This workaround has stopped looping behavior in some cases.(5)
To get direct help with your specific calls:
- Visit Documentation
- Ask questions on Discord
- Visit Hire certified Retell partner
Share your call IDs with the Retell support team on Discord for detailed analysis of what’s happening in your specific flow.(7)