langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

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

New Issue
Closed
opened 2026-02-21 18:20:32 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 18:20:32 -05:00
Owner
Copy Link
Copy Source

Originally created by @jafrank88 on GitHub (Dec 27, 2024).

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.

Originally created by @jafrank88 on GitHub (Dec 27, 2024). ### Self Checks - [X] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] 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.
yindo added the 🐞 bug label 2026-02-21 18:20:32 -05:00
yindo closed this issue 2026-02-21 18:20:32 -05:00
yindo commented 2026-02-21 18:20:32 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (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

@dosubot[bot] commented on GitHub (Dec 27, 2024): <!-- Answer --> 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 <sup>[[1]](https://github.com/langgenius/dify/blob/main/api/tasks/retry_document_indexing_task.py)</sup><sup>[[2]](https://github.com/langgenius/dify/blob/main/api/tasks/batch_create_segment_to_index_task.py)</sup>. 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 <sup>[[3]](https://github.com/langgenius/dify/blob/main/api/services/dataset_service.py)</sup>. 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. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/7e9f83da-a3ba-4bea-b8c8-dd7471e4a596?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/7e9f83da-a3ba-4bea-b8c8-dd7471e4a596?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/7e9f83da-a3ba-4bea-b8c8-dd7471e4a596?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/7e9f83da-a3ba-4bea-b8c8-dd7471e4a596?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/7e9f83da-a3ba-4bea-b8c8-dd7471e4a596?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/7e9f83da-a3ba-4bea-b8c8-dd7471e4a596?feedback_type=other)</sup>
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#7427
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?