### Answer
There was a known issue where Conversation Flow agents could stay silent after function nodes due to a message order issue when a function and response happened at the same time [(1) ](
) . This was resolved, but if your global function node suddenly stopped transitioning, here are key troubleshooting steps:
Check Transition Conditions:
- For function nodes, transition timing depends on your
Wait for Result and
Speak During Execution settings [(2) ](
)
- If
wait for result is turned on, the agent will transition once the function result is ready
- If
wait for result is turned off and
speak during execution is off, the agent transitions immediately after the function gets invoked
- You can write transition conditions based on the function result
Common Issues:
- Similar cases in the community showed this can be caused by the custom function returning data in an invalid format that the node can't process [(3) ](
)
- One user resolved their issue by fixing a JSON schema problem in their tools - Retell showed no error or warning about it
- Global nodes can be configured with transition conditions, and if your condition isn't being met, the agent won't transition [(4) ](
)
Recommended Actions:
1. Verify your custom function is returning valid JSON in the expected format [(5) ](
)
2. Check your transition condition on the global node - ensure it's not stuck because the condition evaluates to false
3. Review your function's re