Unavailable Text-embedding model in Knowledge

[AndyMik90]

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

0.8.0

Cloud or Self Hosted

Cloud

Steps to reproduce

✔️ Expected Behavior

Use the model that was set in step two of creating the knowledge.

❌ Actual Behavior

Have to go into the knowlegde after it's created and set the embedding model again.

[dosubot[bot]]

I found some similar issues that might help:

1. The embedding model isn't saved while creating a Knowledge (closed) - The suggested solution was to check for dirty data when using the same file to create a new Knowledge dataset. It worked well with another file ^[1].
2. Default model not found for ModelType.TEXT_EMBEDDING (closed) - The solution was to configure the default embedding model in Settings -> Model Provider -> System Models ^[2].

For your specific issue in Dify version 0.8.0, the text-embedding model is unavailable in the "Knowledge" section when creating knowledge via Webhook because "the default embedding model needs to be configured."

unavailableTip: 'Embedding model is not available, the default embedding model needs to be configured',

Additionally, ensure that the rate limit for the Embedding model API key has not been reached, as this can also cause issues with embedding model availability ^[3][4].

To continue talking to Dosu, mention @dosu.

[crazywoola]

@AndyMik90 https://github.com/langgenius/dify/issues/8175 Did you encounter something like this issue?

[AndyMik90]

@AndyMik90 #8175 Did you encounter something like this issue?

Yes

[AndyMik90]

@crazywoola could this have something to do with the "deprecated" field for models?

[crazywoola]

Please try v0.8.3, it seems @JohnJyong had fixed this issue.