Skip to content
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

Possible issue with # of words not being recalculated after retry #12174

Open
5 tasks done
jafrank88 opened this issue Dec 27, 2024 · 1 comment
Open
5 tasks done

Possible issue with # of words not being recalculated after retry #12174

jafrank88 opened this issue Dec 27, 2024 · 1 comment
Labels
🐞 bug Something isn't working

Comments

@jafrank88
Copy link

Self Checks

  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • 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).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.13.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Create RAG. Let it process for a bit and then stop it. When you go back to continue and get the 'retry' prompt, agree. The tags beside the individual documents will change from Indexing -> Queuing -> Available but the # of words in that Knowledge Base does not increment the way it does when it is initially processing.

✔️ Expected Behavior

I expected the # of words to increase when more RAG is made available. I used this as a way to tell when processing is done.

❌ Actual Behavior

The number of words is static in the knowledge overview of all RAG segments even though more RAG in that section is being made available on an ongoing basis.

@dosubot dosubot bot added the 🐞 bug Something isn't working label Dec 27, 2024
Copy link

dosubot bot commented Dec 27, 2024

The issue you're experiencing with the word count not updating after a retry in the RAG processing workflow might be related to how the system handles retries and updates the word count. There is logging and error handling in place that could provide insights into why the word count is not updating during retries. The code uses the logging module to log information about the retry process, and exceptions are caught and logged. This can help diagnose issues during the retry process [1][2].

The word count update function is expected to increment the document's word count by the word count of the new segment when new RAG segments are processed [3]. If this is not happening during retries, it might be worth checking the logs for any errors or exceptions that could be affecting this process.

To continue talking to Dosu, mention @dosu.


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

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

No branches or pull requests

1 participant