Share feedback, ideas and get community help

Updated 12 months ago

WhatsApp double flow

At a glance

The community members have identified a bug in a bot that causes it to initiate a second flow in the middle of the first one, duplicating all messages. This issue seems to occur only when there is a prolonged gap between user interactions. The community members have explored this bug by creating their own bot and testing it on WhatsApp and the web version. They have found that the issue occurs on WhatsApp, especially when there are many messages or a long delay between them, but not on the web version.

The community members have discussed potential solutions, including migrating from a serverless environment and increasing the timeout. However, the migration is an important change that cannot be rushed, and the community members are actively working on it. The expected deployment is in a week or in February, but one community member has a strict deadline and may need to consider other options.

Useful resources
In certain situations (I'm not sure about the specific conditions yet), when interacting with the bot through WhatsApp, the bot initiates a second flow in the middle of the first one, duplicating all messages. At first glance, it appears that this issue occurs only when there is a prolonged gap between user interactions.

Is there a known bug related to this?
Attachment
image.png
V
m
B
23 comments
I have created this bot to explore this bug.
First I define how many messages it should send me.
Then the delay between the messages.
On the web version it always works as expected.
With Whatsapp it works if I have few messages or a small delay.
Attachment
image.png
Otherwise it may start a second flow.
Attachment
image.png
There is a bug, even for a simple bot is not working.

I am receiving the message instantly
Attachment
image.png
This works for me, the message is delayed.
You can see by the messages timestamps that the delay works.
Attachment
image.png
just work if I send a message first
Attachment
chrome_uaPgclo6rC.gif
It seems to be working, of course such a small waiting time can have big changes, it depends on processing, networking and communication between applications
If you put 5 minutes, and it is sent in 10, this indicates a problem, but between 5 and 6 is reasonable.
works with this way to me now
Attachment
image.png
This is unfortunately a known issue
This is why we are migrating from serverless environment
I'm actively working on this migration
Thank you!
Do you have an expected due date for this?
I really don't mean to rush you; I'm just asking because I have a very strict deadline to present a MVP to the big guys, and without this fix, I should probably juts pull it off already.
At best it will be deployed in a week
In February, for sure
I have only 6 days. 😆
Better quit.
Yeah sorry, that's an important one, I can't rush it!
Don't worry. That's clearly a sensitive change, can't be rushed.
There's no way to increase the 10s timeout?
I know it's not a final solution, but at least we can manage it by now.
Add a reply
Sign up and join the conversation on Discord