Having an issue during deployment where bot tends to ask the same question multiple times. Works fine in emulator but telegram, messenger, and weblinks have this issue many times. Eg- Bot asks to enter name and email, user enters those, but the bot asks them to do it again. Any help would be appreciated.

Hey, can you share a screenshot of your workflow?

Getting the same issue

🆙

Same issue here, on whatsapp mainly, but sometimes on webchat

Same issue here, when exporting and importing it does go away but then starts acting up again I actually have a problem also that it will randomly start to translate the language to english (i'm building it in hebrew) - also happens even if u set the language at the start node lastly when exporting-importing my last project the new imported project will work fine in studio but in share bot it won't respond at all

Are you sure that after asking for confirmation you are not sending the user to the same node where you ask about their struggles?

ok, let me check.

If that's the case, then we really have a bug on our hands!

because, that is something which have always worked well, that way.

I'm sure that after asking for confirmation leads to a next node. I also attached the bpz file for my bot if you wanna take a look at that. Like I said, emulator works perfectly fine. Its only the integrations that have these issues.

Same situation here, can’t show it to clients

I hope they find solution😔

Hey guys, just a heads up to tell you that we are actively working on this. There are some small differences between the emulator and the webchat. Right now, if you wait 35 minutes after the last message you sent, it should work like it does in the emulator . Will keep you posted

Thanks!! Will this fix the issues on the meta integrations too?

@dazzling-doctor-79129 I believe this issue affects every integration on the cloud. We pushed a fix like 10 mins ago in relation to that. I can give a brief explanation of what was happening. There was 2 different timeouts: the session and context timeout. The session timeout was set at 30 min, and the context timeout was configured at 5 min. The session stores workflow variables and a lot of other information, including the status of prompts on the workflow. The context stores the user's position on the workflow (the current node, card, etc). So, what happened is that you start a conversation with the bot. You end up on a prompt, you go to do something else on another tab, or whatever. Then the context is reset, you restart at the beginning, but your previous prompt is still active in the session, even if you start at the beginning. So if you have multiple prompts active at the same time, or raw inputs, and depending on history lookback, it could cause some issues. We implemented two different fixes for that. 1. 2 timeouts for almost the same thing was too complicated for nothing, so we merged both timeouts, and it has been renamed "Inactivity Timeout" (default: 30m). When this timeout expires, most informations are cleared: chat history, workflow variables, workflow position, etc This can be configured in the bot settings. Note that user and bot variables are not affected by this. 2. Captures are now scoped to the currently active workflow AND the capture card, instead of just the capture card. If you leave a workflow and come back to it through another one, then it will be considered a new workflow and the capture will not have been initiated. (this what was causing random issues, for some users in some situations, hard to reproduce) Please let us know if you have issues @here

I still experiencing the issue

Thanks @colossal-activity-12523 for the good news and the feedback. I will check and get back to you

@colossal-activity-12523 I am still facing this issue. Please help

I am also facing the same issue @colossal-activity-12523

same issue but im not using ai task card or KB, it just cant extract the field and retries the prompt to no avail

Please reload and retry, it should work nwo

hi, sorry it's still not working, the result node is the capture card and it should go to user-choice node.

can you send me your bot export? i'll check it out

like a single choice from the results of ai task

I was facing the same issue till last night but finally figured it out and solved it. Hello 👋, I'm Elijah. I'm available to help out anyone with any issues with Botpress. You can reach out to me; https://cutt.ly/9wpZlWWy

its also in the emulator

Hi, I am still experiencing the same issue

got the same issue. what is the solution?

still have same issue

We found the main culprit for the repetion problem. please try to reload the studio and republish your bot

thanks

It's working better now. It repeats less often

I confirm. It repeats less often. With the insight from @rich-battery-69172 , i also had to correct my capture information cards, because in most cases when it leads to a choice from the user, it is best to capture it as single choice instead of it just be raw input. this contributed to reduce the frequency of messages repeated.

Hey if it repeats again (even if only once) please let me or @colossal-activity-12523 know! Include a screenshot of the emulator and workflow if possible. @dazzling-doctor-79129

yeap, now it's working perfectly fine

hello, what was the main culprit?