Can't publish the workflow without setting the reranking model

[huu3301]

Self Checks

• [x] This is only for bug report, if you would like to ask a question, please head to Discussions.
• [x] I have searched for existing issues search for existing issues, including closed ones.
• [x] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [x] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• [x] Please do not modify this template :) and fill in all the required fields.

Dify version

v1.1.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

1. Start a new deployment from the v1.1.0 version.

2. Upgrade to the v1.1.1 version.

3. Do not set the Rerank Model in System Model Settings.

4. Use the economical index for RAG.

5. Create a workflow and add the knowledge retrieval node.

6. Publish the workflow.

7. Refresh the webpage.

8. Publish the workflow again.

This issue is similar to the ones below: https://github.com/langgenius/dify/issues/15842 https://github.com/langgenius/dify/issues/16018

These issue pages showed that they had been fixed. In fact, it has not been fixed in v1.1.1 yet.

✔️ Expected Behavior

I can publish the workflow without setting the rerank model.

❌ Actual Behavior

No response

[dosubot[bot]]

In Dify version 1.1.1, the requirement to set a Rerank Model when publishing a workflow is due to the configuration of the Knowledge Base Retrieval Node. Specifically, if you are using the multi-way recall mode, a Rerank model is necessary for result re-ranking. This is not a bug but a required configuration for certain retrieval strategies. If you are not using the multi-way recall mode, ensure your configuration aligns with the N-to-1 recall mode, which does not require a Rerank model ^[1][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}

[DavideDelbianco]

I want to EMPHASIZE point n°7 The error happens on already published workflows after you RELOAD the flow schema. The first time you publish the workflow and keep publishing without reloading the schema, it gives no errors

[WTW0313]

Hello, @huu3301 @DavideDelbianco . We are currently working on resolving this issue. In the meantime, you might try opening the panel of the knowledge retrieval node to pass the verification. If you need any assistance, please don't hesitate to reach out.

[DavideDelbianco]

A quick fix is to simply get a reranking model that will never be used like jina or cohere