Chatbot Orchestrate External Knowledge will disappear

[mlzxdzl]

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

1.10

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I set a external knowledge in the Chatbot Orchestrate Retrieval setting. Everything is ok up to now. It will answer my question by use knowledge. But when i refresh the page or reopen the page, the Chatbot Orchestrate Retrieval setting will disappear like following . When it disappear, It can not answer my question by use knowledge, everything going wrong. I found the question in version 1.0/1.0.1/1.10. I beg for someone to help me , it is very important to me

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

[dosubot[bot]]

I found a similar open issue titled "Workflows that include knowledge bases cannot view referenced documents" ^[1]. However, no solution has been found in the comments of that issue.

For your specific problem, it seems like the Chatbot Orchestrate Retrieval settings are not persisting across page refreshes or reopenings. This could be related to how the settings are being saved or retrieved. The function responsible for saving these settings is the handleSave function within the ModifyRetrievalModal component ^[2]. Additionally, the Dify application retrieves and applies saved settings using the chrome.storage.sync.get method ^[3].

You might want to check if there are any errors in the console or logs that could provide more insight into why the settings are not being persisted.

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}

[JohnJyong]

I'm very sorry about this. Due to the upgrade of some of our components, this issue will be delayed until next week and will be fixed as soon as possible. @mlzxdzl