Yes, I’ve seen this happen before. In most cases it’s a transcript rendering or streaming sync issue rather than the actual conversation context being processed incorrectly during the live call. Delays from STT/TTS providers, async tool calls, or websocket timing can make messages appear out of order in the debugger.
That said, it’s still worth checking because if context memory or interrupt handling is misconfigured, it can also affect live behavior. I can help you trace where the ordering issue is coming from and verify whether it’s only visual or actually impacting the agent logic.
@Devin