Conversation flow gets stuck

Support Help
1

Conversation flow gets stuck in a loop even when user asks about a different question unrelated to direct global node please help

2

This is a known issue with conversation flow agents. Based on community reports, looping behavior has been observed particularly with global nodes and split nodes.(1)

Common causes of looping:

  1. Global node with split node interaction - When a split node follows a global node, the flow can incorrectly loop back to the global node even when conditions shouldn’t trigger it.(1) The Retell team has acknowledged this issue and mentioned implementing changes to disable global nodes on split logic.(1)

  2. Transition condition confusion - Complex transition conditions between nodes can confuse the model, causing it to loop rather than progress.(1)

  3. Skip response enabled on global nodes - Global nodes with skip response enabled connecting to function nodes and split nodes have shown looping behavior.(1)

Potential workarounds:

  • Add transition fine-tune examples to help clarify when transitions should occur.(1)
  • Add an additional conversation node after the global node, which has stopped looping in some cases.(1)
  • Simplify node content and make nodes smaller with less content.(2)
  • Review your transition conditions to ensure they’re clear - equation conditions are evaluated first (top to bottom), then prompt conditions.(3)

If the issue persists, share your call ID with the Retell team for investigation. The looping can occur randomly and isn’t always reproducible.(1)

**

3

Hello @umaraziz

Can you share the call id that has this issue?

4

call_2895242927a37cc2e1f1bb2cb03, call_035a5c18771ee5b993f6c7d4b2e

5

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:

  1. 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)

  2. 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)

  3. 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)

  4. 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)

  5. 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:

Share your call IDs with the Retell support team on Discord for detailed analysis of what’s happening in your specific flow.(7)

6

Hello @umaraziz

I can’t identify where the issue is exactly. Please provide the timestamp and the expected behavior you want.

But usually, the stuck on the node happens when the transition condition is not met.

7

Hello @umaraziz

You’re correct that nodes getting stuck typically happens when transition conditions aren’t met(1). To help identify the issue, here are the key diagnostic steps:

Check Your Transition Conditions

Review the transition_condition.prompt field for your edges—the condition field is not used by the LLM to trigger transitions(2). Ensure your prompt is concise, declarative, and matches actual language patterns the user would say(2).

Common Solutions for Stuck Nodes

When node transitions aren’t working as expected(1):

  • Review your transition conditions to ensure they precisely match your intended triggers(1)
  • Add transition finetune examples to help the model understand your expectations(1)
  • Make transition conditions more flexible and general(1)
  • Add more nodes to cover edge cases, particularly global nodes for handling unexpected situations(1)

For Dynamic Variable Issues

If you’re using dynamic variables in your transition conditions, the node may be waiting for a user response before it can transition(3). The variable needs to be populated and the user needs to provide input for the transition to evaluate(3).

Debugging Steps

You can find node transitions inside the call transcript in the history tab, which will show the node names that it transitions from and to(2). This helps identify exactly when transitions occur or fail(2).

If Instructions Aren’t Being Followed

If the agent isn’t following instructions within a node before transitioning(1):

  • Split the node into multiple nodes for better consistency(1)
  • Change the node model to a more capable LLM(1)
  • Add conversation finetune examples(1)
  • Adjust the LLM temperature if responses are inconsistent(1)

To provide more specific guidance, share the call ID and describe the expected behavior at the specific timestamp where the node gets stuck.