knowledge database shows deprecated sign when workspace rereank model not set and rerank model mode selected in retrieval setting #6679

Closed
opened 2026-02-21 18:16:49 -05:00 by yindo · 5 comments
Owner

Originally created by @AkisAya on GitHub (Nov 11, 2024).

Originally assigned to: @crazywoola on GitHub.

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

main

Cloud or Self Hosted

Self Hosted (Source)

Steps to reproduce

  1. do not configure workspace rerank model
  2. in a knowledge dataset retrieval setting, select rerank model mode

0zm6b12000gm9l3rw9E68

✔️ Expected Behavior

lead user to configure a rerank model just like we do when we want choose a text-embedding model

Actual Behavior

just like the image shows

Originally created by @AkisAya on GitHub (Nov 11, 2024). Originally assigned to: @crazywoola on GitHub. ### 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 main ### Cloud or Self Hosted Self Hosted (Source) ### Steps to reproduce 1. do not configure workspace rerank model 2. in a knowledge dataset retrieval setting, select rerank model mode ![0zm6b12000gm9l3rw9E68](https://github.com/user-attachments/assets/40115c2a-2a34-48dd-a331-1f0e21d04568) ### ✔️ Expected Behavior lead user to configure a rerank model just like we do when we want choose a text-embedding model ### ❌ Actual Behavior just like the image shows
yindo added the 🐞 bug label 2026-02-21 18:16:49 -05:00
yindo closed this issue 2026-02-21 18:16:49 -05:00
Author
Owner

@dosubot[bot] commented on GitHub (Nov 11, 2024):

The issue you're experiencing, where the knowledge database shows a deprecated sign when the workspace rerank model is not set and the rerank model mode is selected, is due to the system expecting a valid rerank model configuration. When the rerank model mode is selected, the system requires a configured rerank model to perform semantic reordering of the retrieved document results. Without this configuration, the system cannot perform the reordering, which may trigger a deprecated sign indicating an incomplete setup [1][2].

To resolve this, you need to configure the rerank model by following these steps:

  1. Configure the Rerank Model:

    • Go to the "Model Providers" page.
    • Enter the API Key for the rerank model (e.g., Cohere, Jina AI).
  2. Set the Rerank Model in Retrieval Settings:

    • Navigate to the "Dataset -> Create Dataset -> Retrieval Settings" page to add the rerank settings.
    • Configure the TopK parameter and Score Threshold as needed.

These steps should help guide users to configure a rerank model, similar to how they would configure a text-embedding model [3][4].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Nov 11, 2024): <!-- Answer --> The issue you're experiencing, where the knowledge database shows a deprecated sign when the workspace rerank model is not set and the rerank model mode is selected, is due to the system expecting a valid rerank model configuration. When the rerank model mode is selected, the system requires a configured rerank model to perform semantic reordering of the retrieved document results. Without this configuration, the system cannot perform the reordering, which may trigger a deprecated sign indicating an incomplete setup <sup>[[1]](https://github.com/langgenius/dify/blob/main/web/app/components/workflow/nodes/knowledge-retrieval/utils.ts)</sup><sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/en/guides/knowledge-base/create-knowledge-and-upload-documents.md)</sup>. To resolve this, you need to configure the rerank model by following these steps: 1. **Configure the Rerank Model:** - Go to the "Model Providers" page. - Enter the API Key for the rerank model (e.g., Cohere, Jina AI). 2. **Set the Rerank Model in Retrieval Settings:** - Navigate to the "Dataset -> Create Dataset -> Retrieval Settings" page to add the rerank settings. - Configure the **TopK** parameter and **Score Threshold** as needed. These steps should help guide users to configure a rerank model, similar to how they would configure a text-embedding model <sup>[[3]](https://github.com/langgenius/dify-docs/blob/main/en/learn-more/extended-reading/retrieval-augment/rerank.md)</sup><sup>[[4]](https://github.com/langgenius/dify-docs/blob/main/en/guides/knowledge-base/integrate-knowledge-within-application.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
Author
Owner

@AkisAya commented on GitHub (Nov 11, 2024):

i figure out that this is a bug.
Snipaste_2024-11-11_19-27-58
acutall defaultModel is alway not empty because even though it's not configured, it will be the value like this, a non empty struct with all fields empty string

{
 "provider": "",
 "model": ""
}

Instead of showing the deprecated sign, it's more likely that we tell users to configure at least a rerank model for the workspace like we do for the text-embedding model when it's not set

@AkisAya commented on GitHub (Nov 11, 2024): i figure out that this is a bug. ![Snipaste_2024-11-11_19-27-58](https://github.com/user-attachments/assets/5091d802-c09b-423d-a2d5-d9a8f28b9550) acutall defaultModel is alway not empty because even though it's not configured, it will be the value like this, a non empty struct with all fields empty string ```json { "provider": "", "model": "" } ``` Instead of showing the deprecated sign, it's more likely that we tell users to configure at least a rerank model for the workspace like we do for the text-embedding model when it's not set
Author
Owner

@crazywoola commented on GitHub (Nov 11, 2024):

Feel free to open a PR for this.

@crazywoola commented on GitHub (Nov 11, 2024): Feel free to open a PR for this.
Author
Owner

@dosubot[bot] commented on GitHub (Dec 12, 2024):

Hi, @AkisAya. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary

  • A deprecated sign appears in the knowledge database when the rerank model is not configured.
  • The expected behavior is to prompt users to configure a rerank model, similar to the text-embedding model setup.
  • I provided configuration steps, but you noted the default model is never truly empty.
  • Crazywoola suggested you open a pull request to address the issue.

Next Steps

  • Please confirm if this issue is still relevant to the latest version of the Dify repository by commenting here.
  • If there is no further activity, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Dec 12, 2024): Hi, @AkisAya. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog. I'm marking this issue as stale. **Issue Summary** - A deprecated sign appears in the knowledge database when the rerank model is not configured. - The expected behavior is to prompt users to configure a rerank model, similar to the text-embedding model setup. - I provided configuration steps, but you noted the default model is never truly empty. - Crazywoola suggested you open a pull request to address the issue. **Next Steps** - Please confirm if this issue is still relevant to the latest version of the Dify repository by commenting here. - If there is no further activity, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
Author
Owner

@johnnashautomation commented on GitHub (Jun 30, 2025):

Hi, I had the same issue in Ollama 0.0.5 version.
In the Plugins page if you delete Ollama and Re-Install it. Ollama 0.0.6 will installed (by this message written)
Then if you open Settings page and open Model Provider section and you can click on Ollama then you can see the models will appear on there.
So that you can check your Workspaces everything should be fine.
I hope that helps

@johnnashautomation commented on GitHub (Jun 30, 2025): Hi, I had the same issue in Ollama 0.0.5 version. In the **Plugins** page if you delete Ollama and Re-Install it. Ollama 0.0.6 will installed (by this message written) Then if you open **Settings** page and open **Model Provider** section and you can click on Ollama then you can see the models will appear on there. So that you can check your Workspaces everything should be fine. I hope that helps
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#6679