Hello, I’m experiencing a significant issue with the transition for one of our most important nodes that is consistently experiencing very high latency for almost no apparent reason. All of our other node transitions have normal latency of around 1 second, but this particular node transition is consistently experiencing latency of around 5 to 6 seconds every time, causing significant disruption to the call flow and a worse consumer experience. The issue is specifically with the “ID Verification (DOB or SSN)” node transitioning to either our Conversation Disclosure node or the RPC Reached node. I’ve provided a few call IDs below for your examination: call_0f94a264e8d412ef4d32a3b6736 call_4edc748215926f346f4d5f995bc call_8135be6e57f3475d6e2e6e1a8a1 call_234b241a353695960edffe32c1f I’ve tried a number of modifications to resolve this issue, including reducing the number of transition edges down to two, switching the conversation to static prompting, and changing the transition to go directly to a static conversation node rather than a different component, but none of these changes have worked. I have a similar node in another agent that consistently experiences normal latency of around 1 to 2 seconds for the same transition, but this node is always experiencing 5 to 6 seconds even though it’s nearly identical aside from being in a different agent setup. This leads me to believe this is either a bug on Retell’s end or an edge case with the configuration that someone from Retell support can help identify and resolve. If your team can look into this so we can resolve it, I would greatly appreciate it.

From what you’ve described, the 5–6s delay usually points to backend processing or an external dependency being hit during that specific node’s transition (for example: verification logic, data lookup, or a webhook/API call tied to the ID Verification node). Since an almost identical node in another agent doesn’t show the delay, it does sound like either a configuration edge case or a platform-side issue affecting this agent. To narrow it down quickly: Does the ID Verification (DOB or SSN) node in this agent call any external service, function, or webhook (even indirectly) that the other agent’s node does not?

Hey @Sean OBrien I pass your issue to team to see

Hi @Shehroze -Support @Retell I tested it out again and am still experiencing the latency issue with this node transition. See example call I just did: call_94c75411163f4166ed1577b8653

Thanks for confirming. Since the configurations are identical and there's no external service difference, this does seem like either an agent-level config issue or a platform bug. I'd be happy to take a deeper look at your agent setup and call logs to help pinpoint the root cause. Feel free to DM me if you'd like me to review this privately I've dealt with similar latency issues before and can usually identify the problem quickly

@Shehroze -Support @Retell Just wanted to follow up on this since we're still experiencing the latency issue on this node. Example: call_94c75411163f4166ed1577b8653

Hi @Sean OBrien so the latency is around 1121 , which is within the normal range. The node that is taking a little bit of time becuase you are extract dynamic variable node between transitions

Hi @Shehroze -Support @Retell I don't think that's correct. I adjusted it so that it no longer has an extract dynamic variable node between and instead goes directly to the Balance Disclosure node once they provide the last 4 digits of their social security number, and it still has a 4 to 5 second delay. Here is the call_id for reference: call_0a79f75eb8b55753cdaa1999ada I also took a screenshot of the logs and you can see that the latency on the transition is 4071 miliseconds, which is very high https://cdn.discordapp.com/attachments/1463003760342077597/1464030970578735321/Screenshot_2026-01-22_at_5.53.11_PM.png?ex=6973fc97&is=6972ab17&hm=2050d4d96016a11ed273590b449df3d8b28897f6fb861b7c0df04653a68cd430&