Skip to content

[Bug]: some keywords can't return from ragflow to dify #6595

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
4 tasks done
cryptowww opened this issue Mar 27, 2025 · 2 comments
Open
4 tasks done

[Bug]: some keywords can't return from ragflow to dify #6595

cryptowww opened this issue Mar 27, 2025 · 2 comments
Labels
🐞 bug Something isn't working, pull request that fix bug.

Comments

@cryptowww
Copy link

Self Checks

  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report (Language Policy).
  • Non-english title submitions will be closed directly ( 非英文标题的提交将会被直接关闭 ) (Language Policy).
  • Please do not modify this template :) and fill in all the required fields.

RAGFlow workspace code commit ID

d683644

RAGFlow image version

v0.17.0

Other environment information

macos, docker

Actual behavior

I have build a KB with 300+ documents in md format, every document's size is from 5k t0 30k, an I have turn on auto keywords with 10.

when I connect it from dify, some keyword will trigger an error about can't connect to ragflow, most of key words works well, I don't konw why.

Expected behavior

return correctly.

Steps to reproduce

maybe more files in a kb will trigger this bug?

Additional information

No response

@cryptowww cryptowww added the 🐞 bug Something isn't working, pull request that fix bug. label Mar 27, 2025
Copy link

dosubot bot commented Mar 27, 2025

The issue you're experiencing with some keywords not returning from RAGFlow to dify could be related to several factors:

  1. Keyword Extraction: RAGFlow uses a keyword extraction process that might filter out certain keywords if they don't meet specific criteria, such as the minimum match threshold or token length. This could result in some keywords not being effectively extracted or used [1].

  2. Connection Issues: There might be connection issues between RAGFlow and dify. RAGFlow has a mechanism to handle connection retries, attempting to connect multiple times with delays in between. If the connection is not established, it logs an error and raises an exception [2].

  3. Error Messages: If there are network anomalies, specific error messages are documented, such as "Netzwerkanomalie" (Network anomaly), which might indicate a problem with the connection [3].

To troubleshoot, you might want to check the logs for any error messages related to connection issues and ensure that the keywords are being extracted correctly. Additionally, consider reviewing the configuration settings to ensure they are optimized for handling large document sets.

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@KevinHuSh
Copy link
Collaborator

Did you have backend error logs?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working, pull request that fix bug.
Projects
None yet
Development

No branches or pull requests

2 participants