Global Node -> "Go Back Condition"

Support Help
1

Is anybody experiencing issues with Global Node → “Go Back Condition”?
Mine is not firing no matter what I put in.

This makes Global nodes that are meant to handle something and go back completely unusable. The agent gets stuck in Global node 100% of the time.

I’m not sure what else to do.

Here’re examples of exit prompts I tried:

”The caller is ready to move on to something else”
”The agent has answered the caller’s question about the firm’s general information.”

Please advice!

2

I understand your frustration—you’re experiencing a known limitation with Global Nodes in Conversation Flow.

The Core Issue:

Retell AI currently does not support returning from Global Nodes to the original conversation flow position.(1) This is an architectural limitation of the platform.(1)

What’s Happening:

When you enable “Go Back Condition” on a Global Node, you’re configuring it to transition back to a previous node. However, the “Go Back Condition” feature has specific requirements that may not be working as expected in your setup.(2)

One community member found that the “Go Back Condition” doesn’t work on components or items that have no prompt in them.(2) The condition itself needs to be properly configured to know when to return to the original node.(2)

Workaround Suggested by the Community:

A user shared a workaround for tracking and returning to previous nodes:(3)

  1. Define a variable like last_node in your first prompt node
  2. Make it evolve among all prompt nodes to store the last node name/id
  3. After any global node, link a branch node with prompt conditions checking the last_node value to redirect to the expected node
  4. Note: Equation conditions won’t work with prompt-defined variables, and prompt-defined variables must not use {{}}(3)

Debugging Steps:

For node transition problems in general:(4)

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

Feature Request:

This limitation has been raised by multiple users.(1) You can request this feature be added by submitting a feature request to Retell AI.(1)

3

Hello @info11

Can you share a call id that has this issue?

4

Hi @Omar_Ashraf ,

I ran into this issue while testing (via web call) the “global node” solution.
Since it wasn’t working I was forced to re-engineer it by putting all of that info in the global prompt (instead of global node)

So the current agent no longer has that global node at all.
I’m not sure if the call id’s would still be relevant but here’s the 3 test web calls:

call_7664ad9b610211be3ebcc976ec8
call_22c1ab06d8f93d002e6871e7950
call_6c003b7343c2409123da6676db2

Thanks.

Gene