https://discord.gg/botpress logo
Autonomous Node Querying Wrong Knowledge Base
# 🤝help
s
I am running into an issue with my autonomous node using the incorrect search knowledge card. The problem arose after I reverted from a testing version of my bot to a stable version. Previously, the stable version correctly identified the appropriate knowledge base, but now consistently uses the wrong knowledge base after the reversion. For reference, I have five different knowledge bases and five different search knowledge cards with instructions on when to use that particular knowledge base. To attempt to address this issue, I have reuploaded my knowledge bases, deleted and remade my autonomous nodes and their associated cards. I have also tried creating a new bot with a simplified version of my workflow. In all cases, the incorrect knowledge base is searched for queries that, in the past, lead to my bot using the correct knowledge base. https://cdn.discordapp.com/attachments/1451331440099983361/1451597110553350164/image.png?ex=697b7ca8&is=697a2b28&hm=776cfbb7842b812fa20ce326c2c938698b3777b4c34000919c26572c4a4e2bb7&
I do not have any directions in my system prompt for in-line citations. As can be seen below, the autonomous node identifies the correct knowledge base to search but the returned chunks are from another KB (in this case from a KB related to Solid Waste). I verified by visually inspecting the chunks returned.
l
Update me from our talk in the AMA when you can!
can I get your workspace ID?
s
Here it is Ross: wkspace_01KAY6SMK1MSTE8ZBBCSDMSA4W.
l
Did you end up testing my solution from the AMA?
You can do all this with 1 search knowledge card, just link all the kbs
s
I have tried this in the past and it was an option, but it was more computationally expensive.
Thank you for the help. I did have some success troubleshooting last night by removing some of the KB search cards and restricting the scope to fewer knowledge bases. However, whenever I have all five KB search cards, the autonomous node gets confused. This confusion is despite me providing the autonomous node a variable that specifically denoted the KB to search.
f
@swift-napkin-75164 did you manage to fix this? Having a similar issue.