Bug? Choice Button to Node Causing Extra KB Respon...
# 🤝help
a
In a raw input card with KB active I have 2 choices one is connected to nothing, so when I click the text of the button is sends to the KB and I get the KB response, this is good, but when I click on the other button that is connected to another node I get a response from the KB that I don't want and I am sent to the other node that I do want to happen, meaning I get 2 messages in the bot, I think in the past when you connected a choice button to a node it did not also search the KB, is this a bug? https://cdn.discordapp.com/attachments/1235935568387506177/1235935569004204032/image.png?ex=66362e32&is=6634dcb2&hm=10418c3be11e7e9f1a315c921d145642d2dcb3d0c648c4a900d42d14ee190f67&
w
in your raw input card, do you have KB query disabled?
b
it's not disabled, as you can see by the little book icon - what happens is that when you select a button, the bot simply receives that as an input
in this case, "Contact us" is the query being made to the KB, for which an answer was found
a
This did not work like this before, in this case how should we use choice buttons in a raw input card when kB is active, the choice button should deactivate KB search if connected to a node, it is not logical to have 2 messages at once from the bot in the webchat , I think this a new problem, what is the fix 😭
w
@acceptable-smartphone-22753 the raw input card has worked that way for at least several months -- I believe if you disable KB query within the raw input card only , the behavior will be as you desire
or alternatively, leave the KB query activated and remove the explicit text card
the way I handle cases like this, is to have a separate KB query card that only is activated under certain circumstances, and have the input card KB query disabled
of course, if your KB includes all the information you might want to be used in a response to the user, leaving the KB query in the input card and removing explicit / deterministic text responses may be the way to go
a
It is not good that things change like this because what happens to deployed bots, they start messing up without us knowing and clients just say AI stuff is only hype and we lose all credibility, we need reliability I am scared to push to new clients we need the basics to work 100% just a simple loop with the KB and some buttons to move to another node and come back to the loop, Botpress should ask the community what basic functions we need and make a few official templates that are maintained by Botpress and are used for example with the Botpress website data, so everyone can use and we can report any errors, today I don't know where I can use a large scale Botpress bot @bumpy-butcher-41910 I think what is missing is real life use case situations with real potential clients, I think your streams are great, Patrick also but a stream and videos about the business of providing AI real world solutions with Botpress I think is missing, strategies to build KB, problems bots can have in production, there is a tone to talk about,
b
thanks for the feedback! just to be clear - we didn't push any changes into production that would have caused this change
a
@acceptable-gold-88171 this is the tread for raw & choice, nice to speak