After creating a new knowledge base, switching the embedding cannot correctly process the documents.

[chattor]

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.10.2

Cloud or Self Hosted

Cloud

Steps to reproduce

When creating a new knowledge base and importing a file, the default embedding cannot be used due to the absence of tokens. However, when switching to a pre-configured embedding model, the preview on the right still does not appear. Additionally, clicking "Process" results in an error, as shown in the image.

✔️ Expected Behavior

After creating a new knowledge base and importing files, you can switch the embedding model and process it normally."

❌ Actual Behavior

After creating a new knowledge base and importing files, switching the embedding model still cannot successfully process the documents.

[dosubot]

I found some similar issues and discussions that might be relevant to your problem:

1. Discussion: Error: Response output is missing or does not contain embeddings - This is an unsolved discussion that might have similar symptoms to what you're experiencing ^[1].

2. Closed Issue: An error occurred while creating a knowledge base with Baidu vector database and Wenxin embedding model - This issue was resolved by a pull request that fixed an unexpected error when creating a knowledge base with specific configurations ^[2].

3. Closed Issue: Lack of clear status indication and re-vectorization option after changing local knowledge base Embedding model - This issue was closed without a solution, but it highlights the need for better status indication when changing embedding models ^[3].

To address your issue, ensure that:

• The embedding model is correctly configured in the Settings --> Model Providers section.
• All necessary credentials for the embedding model are properly set up.
• The model provider you are switching to is supported by Dify and that you have the correct API key and configuration ^[4][5].

If the problem persists, it might be helpful to check the server logs for any specific error messages that could provide more insight into the issue.

To continue talking to Dosu, mention @dosu.