Description:
The agent is navigating component nodes in the incorrect sequence, which is leading to hallucinated responses and conversation flow breakdowns.
Specifically, the agent:
• Enters a component
• Proceeds to the second node
• Then jumps back to the first node
• Becomes stuck in the flow
This incorrect node execution order appears to disrupt state handling and causes the agent to generate responses that are not aligned with the expected logic of the component.
Expected Behavior:
• The agent should enter nodes in the defined sequential order (Node 1 → Node 2 → etc.).
• The flow should complete without looping backward or re-entering earlier nodes unless explicitly designed to do so.
• The agent should not hallucinate content due to improper node sequencing.
Actual Behavior:
• Node execution order is inconsistent (Node 2 before Node 1).
• The agent re-enters previous nodes unexpectedly.
• The flow gets stuck and produces incorrect or hallucinated outputs.
Impact:
• Breaks conversational logic
• Produces unreliable responses
• Prevents successful task completion
Attachments:
• Screenshots demonstrating the incorrect node execution order (see attached images)
Your issue with nodes executing out of sequence and causing hallucinations is related to Conversation Flow transition logic.(1)
Based on the available documentation, here’s what controls node sequencing in Retell AI:
Edges Define Node Transitions
Edges connect nodes and define transition conditions between them, determining how conversations progress based on user interactions.(1) The connectivity ensures conversations flow logically.(1)
Transition Accuracy Metrics
Retell AI tracks Transition Accuracy, which measures the accuracy of transitions between conversation nodes or states.(2) Higher accuracy indicates the agent is following the intended conversation flow correctly.(2)
The system also monitors Node Transition Inaccuracy, which measures incorrect node transitions in conversation flows and helps identify when the agent moves to the wrong conversation state.(2)
Addressing Your Specific Issue
Your screenshots show the agent jumping from Node 2 back to Node 1, then getting stuck. This suggests:
- Edge conditions may not be properly defined between your nodes
- Transition logic might be conflicting or allowing backward movement unintentionally
Recommended Actions
To resolve this:
- Review the edges connecting your nodes and verify the transition conditions are correctly configured(1)
- Test your flow using Retell AI’s testing tools to identify where the transition logic breaks(1)
- Monitor Transition Accuracy and Node Transition Inaccuracy metrics in your analytics to track improvements(2)
The hallucinations you’re experiencing are likely a direct result of the agent being in an unexpected state due to incorrect node sequencing, which causes it to generate responses without proper context.(3)(1)
**
lol this is not correct, this entire call flow is out of order
call_50189c063fa9387bb4b3255b157
