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

Chat/Completion App multiple retrieve rerank switch does not take effect using external kb #14027

New Issue
Closed
opened 2026-02-21 19:15:09 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:15:09 -05:00
Owner
Copy Link
Copy Source

Originally created by @zengruizhao on GitHub (May 19, 2025).

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

1.4.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Configure multiple external knowledge bases in the chat/completion application, turn off the rerank switch of multiple retrieve , and find that the results will still be reranked

Image

✔️ Expected Behavior

The rerank function of multiple retrieve takes effect according to the configuration

❌ Actual Behavior

Configure multiple external knowledge bases in the chat/completion application, turn off the rerank switch of multiple retrieve , and find that the results will still be reranked

Originally created by @zengruizhao on GitHub (May 19, 2025). ### 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 1.4.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Configure multiple external knowledge bases in the chat/completion application, turn off the rerank switch of multiple retrieve , and find that the results will still be reranked ![Image](https://github.com/user-attachments/assets/21ecb7f8-0867-4f47-967e-f85997ebd618) ### ✔️ Expected Behavior The rerank function of multiple retrieve takes effect according to the configuration ### ❌ Actual Behavior Configure multiple external knowledge bases in the chat/completion application, turn off the rerank switch of multiple retrieve , and find that the results will still be reranked
yindo added the 🐞 bug label 2026-02-21 19:15:09 -05:00
yindo closed this issue 2026-02-21 19:15:09 -05:00
yindo commented 2026-02-21 19:15:10 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (May 19, 2025):

Hello @zengruizhao! I'm Dosu, your friendly bot here to help you tackle bugs, answer questions, and guide you on your journey to becoming a contributor. I'm here while you wait for a human maintainer. Let's dive into your issue!

The issue you're experiencing with the rerank switch not taking effect in Dify version 1.4.0 might be related to a bug that was previously identified in version 0.15.3. This bug caused the rerank model switch to automatically turn on due to the reranking_enable setting incorrectly defaulting to true, even when the switch was turned off [1].

To resolve this, ensure that you are using the latest version of Dify, as the issue was addressed in a recent update through PR #13721 [2]. If the problem persists in version 1.4.0, it might be worth checking if similar conditions are causing the rerank model to activate automatically, such as indexMethod being set to 'high_quality', retrievalConfig.reranking_enable being true, or retrievalConfig.search_method being RETRIEVE_METHOD.hybrid [2].

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

@dosubot[bot] commented on GitHub (May 19, 2025): <!-- Greeting --> Hello @zengruizhao! I'm [Dosu](https://dosu.dev), your friendly bot here to help you tackle bugs, answer questions, and guide you on your journey to becoming a contributor. I'm here while you wait for a human maintainer. Let's dive into your issue! <!-- Answer --> The issue you're experiencing with the rerank switch not taking effect in Dify version 1.4.0 might be related to a bug that was previously identified in version 0.15.3. This bug caused the rerank model switch to automatically turn on due to the `reranking_enable` setting incorrectly defaulting to true, even when the switch was turned off <sup>[[1]](https://github.com/langgenius/dify/issues/15586)</sup>. To resolve this, ensure that you are using the latest version of Dify, as the issue was addressed in a recent update through PR #13721 <sup>[[2]](https://github.com/langgenius/dify/issues/13770)</sup>. If the problem persists in version 1.4.0, it might be worth checking if similar conditions are causing the rerank model to activate automatically, such as `indexMethod` being set to `'high_quality'`, `retrievalConfig.reranking_enable` being true, or `retrievalConfig.search_method` being `RETRIEVE_METHOD.hybrid` <sup>[[2]](https://github.com/langgenius/dify/issues/13770)</sup>. <!-- 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/ba430254-dc70-48d2-ab5e-fd68e35d6615?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/ba430254-dc70-48d2-ab5e-fd68e35d6615?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/ba430254-dc70-48d2-ab5e-fd68e35d6615?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/ba430254-dc70-48d2-ab5e-fd68e35d6615?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ba430254-dc70-48d2-ab5e-fd68e35d6615?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/ba430254-dc70-48d2-ab5e-fd68e35d6615?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ba430254-dc70-48d2-ab5e-fd68e35d6615?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#14027
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?