search

botpress / v12

Botpress OSS – v12
https://v12.botpress.com
GNU Affero General Public License v3.0
68 stars 84 forks source link

"Contexts" in Q&A NOT WORKING! #1733

Open shanalexjoseph opened 1 year ago

shanalexjoseph commented 1 year ago

I'm using an open source version of botpress 12.30.7.

Issue:

My issue is with the "Contexts" feature inside Q&A section/tab. The default context is "global" which doesn't have this issue. When I use a custom context, the FAQ doesn't seem to work. However, if I add a "global", along with custom context, then it seems to be okay. But again, the custom contexts are not recognized

davidvitora commented 1 year ago

Hey @shanalexjoseph, are you setting the context in your conversation using the appendContext action? https://github.com/botpress/botpress/blob/master/modules/builtin/src/actions/appendContext.js

shanalexjoseph commented 1 year ago

Hey @davidvitora!, No. When you click on the dropdown of a specific question in the Q&A section, you will see a "Contexts" text box. This is where you can provide a context related to that particular question. This is how I do it. But it's not working

davidvitora commented 1 year ago

@shanalexjoseph You set a context for your question there, but the bot will never answer that question if you don't add that context to the conversation. If you need an example, look at our Welcome Bot template.

image

murali1999-tech commented 1 year ago

Check that the custom contexts have been defined correctly. Make sure that the names of the custom contexts match exactly with how they are referred to in the Q&A section/tab.

Ensure that the intents and questions are associated with the correct contexts. If the intent or question is associated with a context that does not exist or is misspelled, it will not be recognized.

Verify that the custom contexts are enabled in the Q&A section/tab. You can check this by going to the "Settings" section and selecting "Contexts". Make sure that the custom contexts are listed and enabled.

If you are using a version control system like Git, check if there are any changes to the configuration files that may have caused the issue. You can try reverting to an earlier version of the configuration file to see if that resolves the issue.