There appears to be a problem with the WhatsApp Cloud API integration
I'm also having a problem with flow created today and with old self-hosted Typebot with versions 2.24.1 and 2.25.1
I have already generated a new permanent token and created a new connection in flow but without success
Is @Baptiste aware of this problem?
this log was generated when I sent the word that should start the bot
Yesterday I noticed that the bot session integrated with Cloud API is not being closed after the specified time
Ok, this should be escalated as a bug then
When did this problem occur?
It happens when you upgrade to v2.25.0?
hi @Baptiste ,
In my case, I initially observed it on Typebot with 2.25.0... I updated it to 2.25.1 but the problem persists
I'm also having a problem with 2.24.0
Ok I can reproduce the issue.
it happens when i upgrade to Version: 2.25.1, its safe to downgrade version with docker?
No it is not safe as potential database migrations were applied.
In fact, I could not reproduce...
Can you provide a bot example that has this issue?
And exactly how you are testing out?
I tried duplicating the lead gen template, I plugged my WA number, enabled it and it worked
I can send you my flow, is this in Brazilian Portuguese a problem?
@Baptiste
I don't know if there's something specific, but I'm inside a block that I can't exit, I try to type, exit, close, stop and it still doesn't reset the person.
Would there be any way to end the session with a number?
Ok I'm pushing a potential fix now
i already reset the whatsapp integration and new registered webhook from typebot but the error logs still show up, i tested on this simple bot example
My whatsapp integrations stopped as well. How do you check those logs? Is this inside of the container?
This has become a big problem... I noticed that if the user does not finish the flow, even after the time set to end the session has expired, the user number no longer calls the bot
@Baptiste will the fix for this problem be implemented in the next version?
I actually have 2 numbers where this happened and I can't talk anymore.
@Baptiste
hi, hi, any news??
I downgraded to version 2.24.0 and it worked! I am waiting the solution! Tks @Baptiste for this amazing app!
@Baptiste If you need anything else just ask.
Releasing v2.25.2 now (should be available in max 30 min)
Wow good news thanks baptiste
Let me know if that fixes the issue
unfortunatelly it does not worked for me... I tried even the Next release and the error persist 😦
When I sent a message on whatsapp, the log of the viewer just shows me this:
Is currently replying, skipping...
Ok so it sounds like your session is stuck on a "reply" state. Let me push something that will unlock your situation
I did a really simple test and it seems its working...
Thank you, I will check after the pipeline runs.
Confirm new error appears, but my WA bot works on the number that never get the response before
prisma:error
Invalid `prisma.chatSession.createMany()` invocation:
Unique constraint failed on the fields: (`id`)
Something went wrong PrismaClientKnownRequestError:
Invalid `prisma.chatSession.createMany()` invocation:
Unique constraint failed on the fields: (`id`)
at In.handleRequestError (/app/node_modules/.pnpm/@[email protected][email protected]/node_modules/@prisma/client/runtime/library.js:122:6854)
... 8 lines matching cause stack trace ...
at async callRecursive (file:///app/node_modules/.pnpm/@[email protected]/node_modules/@trpc/server/dist/index.mjs:456:32) {
code: 'INTERNAL_SERVER_ERROR',
name: 'TRPCError',
[cause]: PrismaClientKnownRequestError:
Invalid `prisma.chatSession.createMany()` invocation:
Unique constraint failed on the fields: (`id`)
at In.handleRequestError (/app/node_modules/.pnpm/@[email protected][email protected]/node_modules/@prisma/client/runtime/library.js:122:6854)
at In.handleAndLogRequestError (/app/node_modules/.pnpm/@[email protected][email protected]/node_modules/@prisma/client/runtime/library.js:122:6188)
at In.request (/app/node_modules/.pnpm/@[email protected][email protected]/node_modules/@prisma/client/runtime/library.js:122:5896)Is this just a one time error or does it always appear?
it worked. Thank you very much Baptiste. You are the guy.
Yeah just once i already test many conversation and no problem.. so should i pull this new next version?
Don't worry about that error then if you can't reproduce it
Ok nice thanks baptiste youre awesome 🔥
Ok, I am facing a strange error here:
I was using the realease Next.
Everything was working fine.
Then I made a simple change in the flow and when I clicked the publish button, it said that there is nothing to publish. And the button still in Publish state. But the changes appeared on the whatsapp.
After that, the flow stopped to send images to whatsapp.
Then I try to go back to the Latest release. The whatsapp is still working, but the flow stop in the images.
this solved it... thank you very much
Forget about this guys, I just deleted my files by mistake LOL
Hello beauty?
So, I updated the typebot, but I see that with my contacts who already had conversations, it doesn't respond. It happens like this, I sent a message to the bot on WhatsApp, I waited 3 hours with the flow without finishing. When I went to call the bot again it didn't respond anymore. Do you know what it could be?
Can you provide the server logs? There should be a clear error there.
If you are self-hosting it with docker. Type this command in your terminal:
Paste all the logs here so that we can help you properly!
The logs don't show anything, I'm using portainer, and accessing each location only shows the normal log. no mistakes
Same here, i've been having this issue for days, even that the session is configure to 1 hour
i'm using the image avaiable on docker hub
I don't know what else to do. it's hard. hahahaha
I tried deleting the number and configuring it, but to no avail.
Do you have any idea what could be causing this? @Baptiste
You need to pull the next version, it's fixed here
