Autonomous Nodes don’t have built-in timeout handling like regular nodes. The clean way around it is to run a 3-minute delay in the background while the node is active, and track whether the user has replied using a variable or flag. If no response comes in within that window, you automatically push the flow to the next node; if they do respond, you simply prevent that transition from happening.
If you want something more robust, you can also handle the timeout externally (e.g., via a webhook or scheduler) and trigger the next step without interrupting the session. I’ve implemented this kind of logic before, so I can help you set it up smoothly
@flaky-printer-85634