Typebot•10mo ago

Inconsistent Typebot Command execution behavior

Following up with Where are Typebot variables stored? and after playing around with the

sendCommand

sendCommand

sendCommand

sendCommand feature, I'm still trying to see if Typebot's Custom Commands can be used to trigger a call a specific function when needed and then resume/go back to where it was in the flow.

I've tried different settings until I found one that seemed to have the expected behavior... until I restarted my bot's preview several times:
It has an inconsistent/random outcome every time it is executed, as you can see in the video.
Sometimes it calls the function first and then resumes the flow, sometimes it responds first and then calls the function, sometimes it duplicates the bubbles in the command etc. without changing any option — only restarting the bot's preview.

I've tried different combinations:

with/without the
```
Resume flow after
```
Resume flow after
```
Resume flow after
```
Resume flow after
option checked in the Command block
with/without the
```
Pause the flow
```
Pause the flow
```
Pause the flow
```
Pause the flow
option checked on a 0s Wait block

Content of the script block in the flow:

Typebot.sendCommand("nameValidation")

Typebot.sendCommand("nameValidation")

Typebot.sendCommand("nameValidation")

Typebot.sendCommand("nameValidation")

Is it happening because the time it takes to call the command can vary?
I'm curious as to why it's happening and if it's possible using Commands (while waiting for the upcoming Pods feature)

Hall•3/14/25, 1:44 PM

Someone will reply to you shortly. In the meantime, this might help:

AnthonyOP•3/14/25, 1:46 PM

Case where the Command has

Resume flow after

Resume flow after

checked and no Wait block:

Expected result:
text input ➔ function call ➔ success message
Current result:
text input ➔ success message ➔ function call ➔ text input

AnthonyOP•3/14/25, 1:47 PM

Case where the Command has

Resume flow after

Resume flow after

checked and a 0s Wait block with

Pause the flow

Pause the flow

checked:

Expected result:
text input ➔ function call ➔ success message
Current result:
text input ➔ function call ➔ success message ➔ success message

AnthonyOP•3/14/25, 2:08 PM

Hey @!Enzo just wondering if you've got a solution using Typebot

sendCommand

sendCommand

to call a specific function after an input has been filled that does something with the inputted value, then resumes the flow normally.
Your previous use case involved storing a Boolean value in the window.Typebotwindow.Typebot object and then executing a Custom Command conditionally in a setTimeoutsetTimeout, but this time it should always execute and get back dynamically to where it was before executing the command (so a Jump won't work)

AnthonyOP•3/14/25, 2:13 PM

The end goal is to be able to reuse the same Command multiple times in the flow, where it processes inputted (or other) variables in some Script, and then continues the flow

AnthonyOP•3/14/25, 2:31 PM

Hmm, it seems to have the expected result with these options:

A 0.5s Wait block, with
```
Pause the flow
```
```
Pause the flow
```
checked
The Command block with Resume the flow afterResume the flow after checked

AnthonyOP•3/14/25, 2:58 PM

When the "validatedName" variable returned

false

false

from the Command, I'm making it so the flow goes back so asking the user's name with the same text input.
As you can see in the video, it seems to only call the

sendCommand

sendCommand

on the first execution, and never afterwards

!Enzo•3/15/25, 10:02 PM

I haven't had the chance to dive deep into the

sendCommand

sendCommand

behavior yet, just due to lack of opportunity. Could you share the exported flow here? It seems like it should work as expected.

Baptiste•3/17/25, 11:32 AM

I wouldn't use the Command event for that.

Baptiste•3/17/25, 11:32 AM

What I suggest you do is use the Link to Typebot block: https://docs.typebot.io/editor/blocks/logic/typebot-link#link-to-typebot

Baptiste•3/17/25, 11:32 AM

You select current typebot and desired group to execute

Baptiste•3/17/25, 11:33 AM

I used this mechanism in the Skin typology template, check it out!

AnthonyOP•3/17/25, 1:07 PM

OH wow Baptiste, I just tested and it works!
I actually didn't know that the Link to Typebot block would continue the flow after the blocks group it jumped to has finished executing. This info doesn't seem to be explicitly documented. I understood that it would jump to another Typebot and pursue whatever blocks there are, without going back to the blocks before jumping (whereas this was exactly what I wanted to achieve).

This solution is perfect, thanks!

Inconsistent Typebot Command execution behavior

Similar Threads

Similar Threads

Similar Threads