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

[Knowledge Retrieval] Rerank model cannot be empty. #8366

New Issue
Closed
opened 2026-02-21 18:25:16 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 18:25:16 -05:00
Owner
Copy Link
Copy Source

Originally created by @donglirx on GitHub (Feb 18, 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

0.15.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When publishing an application in chatflow, you might encounter the issue '[Knowledge Retrieval] Rerank model cannot be empty,' and the corresponding settings show it as deprecated.

✔️ Expected Behavior

No response

❌ Actual Behavior

Image
Image

Originally created by @donglirx on GitHub (Feb 18, 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 0.15.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce When publishing an application in chatflow, you might encounter the issue '[Knowledge Retrieval] Rerank model cannot be empty,' and the corresponding settings show it as deprecated. ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior ![Image](https://github.com/user-attachments/assets/0f2f3ab6-5b9c-4c5b-8dc9-594384020ade) ![Image](https://github.com/user-attachments/assets/66d0b7fc-43a2-4492-bca1-8b91992dccc0)
yindo added the 🐞 bug label 2026-02-21 18:25:16 -05:00
yindo closed this issue 2026-02-21 18:25:16 -05:00
yindo commented 2026-02-21 18:25:16 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 18, 2025):

Hello @donglirx! I'm here to assist you with any bugs, questions, or contributions. Let's work together to solve this issue.

I found a similar closed issue regarding the '[Knowledge Retrieval] Rerank model cannot be empty' message. The suggested solution was to ensure that the rerank model is properly configured in the retrieval settings. This error typically occurs when the rerank model is not set up correctly, especially when the retrieval mode is set to multiWay [1].

To resolve this issue, you should:

  1. Verify that the multiple_retrieval_config is correctly set up with a rerank model. The system checks if the rerank model is configured when the retrieval mode is set to multiWay.

  2. Ensure that the _datasets and multiple_retrieval_config are correctly populated. If the rerank model is not configured, you will receive an error message indicating that the rerank model field is required.

Make sure that the rerank model is not deprecated and is correctly set in your application's settings. If it is deprecated, you may need to update to a supported model [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 (Feb 18, 2025): <!-- Greeting --> Hello @donglirx! I'm here to assist you with any bugs, questions, or contributions. Let's work together to solve this issue. <!-- Answer --> I found a similar closed issue regarding the '[Knowledge Retrieval] Rerank model cannot be empty' message. The suggested solution was to ensure that the rerank model is properly configured in the retrieval settings. This error typically occurs when the rerank model is not set up correctly, especially when the retrieval mode is set to `multiWay` <sup>[[1]](https://github.com/langgenius/dify/issues/5119)</sup>. To resolve this issue, you should: 1. Verify that the `multiple_retrieval_config` is correctly set up with a rerank model. The system checks if the rerank model is configured when the retrieval mode is set to `multiWay`. 2. Ensure that the `_datasets` and `multiple_retrieval_config` are correctly populated. If the rerank model is not configured, you will receive an error message indicating that the rerank model field is required. Make sure that the rerank model is not deprecated and is correctly set in your application's settings. If it is deprecated, you may need to update to a supported model <sup>[[2]](https://github.com/langgenius/dify/blob/main/web/app/components/workflow/nodes/knowledge-retrieval/default.ts)</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/8e6d432b-cecc-4a52-a24e-330526bd4213?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/8e6d432b-cecc-4a52-a24e-330526bd4213?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/8e6d432b-cecc-4a52-a24e-330526bd4213?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/8e6d432b-cecc-4a52-a24e-330526bd4213?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/8e6d432b-cecc-4a52-a24e-330526bd4213?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/8e6d432b-cecc-4a52-a24e-330526bd4213?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/8e6d432b-cecc-4a52-a24e-330526bd4213?feedback_type=other)</sup>
yindo commented 2026-02-21 18:25:16 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 18, 2025):

fix: reranking_enable setting failed #13668 (#13721)

@crazywoola commented on GitHub (Feb 18, 2025): fix: reranking_enable setting failed #13668 (#13721)
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#8366
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?