Need support for delays between HTTP nodes in the flow
Need support for delays between HTTP nodes in the flow
At a glance
A community member is experiencing an issue with their Typebot flow configuration where HTTP nodes are executed simultaneously, ignoring the configured delays. The expected behavior is for Typebot to respect the delays between HTTP nodes, but the current behavior is that all HTTP nodes are executed at once, regardless of the "No Wait" setting. The community member has questions about whether there are technical limitations preventing delays between HTTP nodes and if there are any alternatives to achieve the desired functionality.
In the comments, another community member mentions that a Typebot developer, Baptiste, has answered this issue on Discord, but the answer is not provided in the given information.
Hello, I’m experiencing unexpected behavior in my flow configuration on Typebot. The issue arises when using HTTP nodes in sequence, with the following setup:
Current flow configuration:
Text message. Configured delay. HTTP node to send audio (with "No Wait" disabled). Configured delay. Another HTTP node, and so on. Problem:
Despite configuring delays between the nodes, Typebot executes all HTTP nodes at once, ignoring the configured delays. This results in the audios being sent without respecting the expected order and timing. Expected behavior:
Typebot should respect the configured delays, even for HTTP nodes, so the flow follows this pattern: Message -> Delay -> HTTP -> Delay -> HTTP. Current behavior:
All HTTP nodes are executed simultaneously, ignoring the configured delays, regardless of the "No Wait" setting. Questions:
Is there a technical limitation preventing delays between HTTP nodes? Are there any alternatives to achieve this functionality in the flow? Additional details:
This issue is critical for flows that rely on messages and audios being sent in a specific order.
