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

maximum recursion depth exceeded in knowledge retrieval with metadata filter #20228

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

Originally created by @yoshio-sugiyama-rb on GitHub (Nov 10, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

v1.9.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  • Create knowledge with 2000 documents.
  • Create Knowledge Retrieval block with metadata filter which hits most of documents.
  • Following error is displayed in API log and nothing return in Knowledge Retrieval.
api-1            | Exception in thread Thread-15118 (_retriever):
api-1            | Traceback (most recent call last):
api-1            |   File "/usr/local/lib/python3.12/threading.py", line 1075, in _bootstrap_inner
api-1            |     self.run()
api-1            |   File "/usr/local/lib/python3.12/threading.py", line 1012, in run
api-1            |     self._target(*self._args, **self._kwargs)
api-1            |   File "/app/api/core/rag/retrieval/dataset_retrieval.py", line 653, in _retriever
api-1            |     documents = RetrievalService.retrieve(
api-1            |                 ^^^^^^^^^^^^^^^^^^^^^^^^^^
api-1            |   File "/app/api/core/rag/datasource/retrieval_service.py", line 107, in retrieve
api-1            |     raise ValueError(";\n".join(exceptions))
api-1            | ValueError: maximum recursion depth exceeded;
api-1            | maximum recursion depth exceeded

✔️ Expected Behavior

  • Retrieve relative documents.

❌ Actual Behavior

  • Retrieve nothing.
Originally created by @yoshio-sugiyama-rb on GitHub (Nov 10, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version v1.9.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce - Create knowledge with 2000 documents. - Create Knowledge Retrieval block with metadata filter which hits most of documents. - Following error is displayed in API log and nothing return in Knowledge Retrieval. ``` api-1 | Exception in thread Thread-15118 (_retriever): api-1 | Traceback (most recent call last): api-1 | File "/usr/local/lib/python3.12/threading.py", line 1075, in _bootstrap_inner api-1 | self.run() api-1 | File "/usr/local/lib/python3.12/threading.py", line 1012, in run api-1 | self._target(*self._args, **self._kwargs) api-1 | File "/app/api/core/rag/retrieval/dataset_retrieval.py", line 653, in _retriever api-1 | documents = RetrievalService.retrieve( api-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^ api-1 | File "/app/api/core/rag/datasource/retrieval_service.py", line 107, in retrieve api-1 | raise ValueError(";\n".join(exceptions)) api-1 | ValueError: maximum recursion depth exceeded; api-1 | maximum recursion depth exceeded ``` ### ✔️ Expected Behavior - Retrieve relative documents. ### ❌ Actual Behavior - Retrieve nothing.
yindo added the 🐞 bug label 2026-02-21 20:06:23 -05:00
yindo closed this issue 2026-02-21 20:06:23 -05:00
yindo commented 2026-02-21 20:06:23 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 10, 2025):

This recursion error in knowledge retrieval with metadata filtering is likely caused by duplicate documents triggering unintended recursion in the retrieval logic. A recent fix was merged that adds deduplication for documents during hybrid search, specifically in retrieval_service.py just after the exception at line 107—right where your error occurs. The deduplication method removes duplicates based on doc_id and document content, which helps prevent recursion issues when large document sets and broad filters are used. Upgrading to the latest version with this fix should resolve the problem. You can review the details of the change here.

If you can't upgrade immediately, try reducing the number of documents or narrowing your metadata filter to avoid matching too many documents, as a temporary workaround.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Nov 10, 2025): <!-- Answer --> This recursion error in knowledge retrieval with metadata filtering is likely caused by duplicate documents triggering unintended recursion in the retrieval logic. A recent fix was merged that adds deduplication for documents during hybrid search, specifically in `retrieval_service.py` just after the exception at line 107—right where your error occurs. The deduplication method removes duplicates based on `doc_id` and document content, which helps prevent recursion issues when large document sets and broad filters are used. Upgrading to the latest version with this fix should resolve the problem. You can review the details of the change [here](https://github.com/langgenius/dify/pull/26360). If you can't upgrade immediately, try reducing the number of documents or narrowing your metadata filter to avoid matching too many documents, as a temporary workaround. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/62cdd748-dc34-438c-bdcf-ec9e936f68b2?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/62cdd748-dc34-438c-bdcf-ec9e936f68b2?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/62cdd748-dc34-438c-bdcf-ec9e936f68b2?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/62cdd748-dc34-438c-bdcf-ec9e936f68b2?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/62cdd748-dc34-438c-bdcf-ec9e936f68b2?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/62cdd748-dc34-438c-bdcf-ec9e936f68b2?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/62cdd748-dc34-438c-bdcf-ec9e936f68b2?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/28035)
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#20228
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?