[Question]: In the knowledge base search test page, the retrieval is successful. However, on the chat page, it returns that nothing is found in the knowledge base, despite the same similarity parameter configuration being used.
Describe your problem
1.Running via Docker on Ubuntu 22.04, tested for multiple days, always fetching the latest code and images. 2.Established the knowledge base using BCE embedding, uploaded PDFs, parsing was successful, search tests were successful, the first result matched. 3.Configured the chat feature, using the same parameters and models as before; with the same query, the information could not be found.
What could be the possible reasons? How should I go about troubleshooting? Thanks
knowledge:
chat:
you can try to change the chat model or making the prompt less limitations
What LLM you're using? LLM can't relate the question and the retrievals though the related answer has been already retrived.
What LLM you're using? LLM can't relate the question and the retrievals though the related answer has been already retrived.
you can try to change the chat model or making the prompt less limitations
Thanks, I used online API: qwen-plus and deepseek-chat, doesn't work either; information can be found in knowledge base retrieval tests, but it just can't be retrieved during chats.
Hi, I had the same problem. Have you solved it yet?
Hi, I had the same problem. Have you solved it yet?
There are two situations, you can add code debugging information, one is to retrieve the chunk but can't answer it, this kind of large model capability problem, change to a large model with strong ability should be able to solve, one is that the relevant chunk information is not retrieved at all, or the retrieved output is other block information, of course, the output will not find the relevant content, the reason may be that RagFlow's own strategy is to retrieve according to the combination of historical problems, which may lead to the weight of the current problem to be reduced
I agree with sznariOsmosis. Close.
需要在提示引擎中配置变量 knowledge