Share feedback, ideas and get community help

Updated 5 months ago

The block is executing first then the others

At a glance

The community member is facing an issue with the execution order of blocks in their Typebot application. When using the view, the blocks execute correctly, but when using the API Reference to start a chat, the blocks execute in a different order, with the community member's block executing first, even though it is the last one. The community member is wondering if they need to pass any parameters to address this issue.

In the comments, another community member suggests referring to the Typebot documentation on webhooks, which explains that this is how the Typebot engine works under the hood. Another community member suggests adding a Wait block with a 0-second pause to ensure sequential execution, without the need for waiting.

Useful resources
I have added a new block with forge and I'm facing a problem. In the run function I'm using a try catch to run what I need and it's working, but, there's a problem with with depending the way I called the chat. If I use the view(attached image), the blocks are executing correctly. Instead of this, if I use the API Reference start chat(https://docs.typebot.io/api-reference/chat/start-chat) my block executes first then the others, even if it's the last one. Should I pass some paramether in this cases?
Attachment
image.png
B
i
p
5 comments
This is how Typebot engine works under the hood
Ok, thanks!
I have the same problem, in this case I need it to be sequential without the need for wait, would that be possible?
Just add a Wait block with pause option but 0s
Add a reply
Sign up and join the conversation on Discord