langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

I chose Jina as the Embedding Model, and the created knowledge base is displayed in the queue. I checked the method you provided above, and I confirmed that it was a fault in the Dify backend. #4630

New Issue
Closed
opened 2026-02-21 18:07:18 -05:00 by yindo · 3 comments
yindo commented 2026-02-21 18:07:18 -05:00
Owner
Copy Link
Copy Source

Originally created by @Sam-gz on GitHub (Jul 16, 2024).

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).
  • 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.6.14

Cloud or Self Hosted

Cloud

Steps to reproduce

Jina

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @Sam-gz on GitHub (Jul 16, 2024). ### 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] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.6.14 ### Cloud or Self Hosted Cloud ### Steps to reproduce ![Jina](https://github.com/user-attachments/assets/504578d3-7a1c-47e1-a883-e67189fd7528) ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 18:07:18 -05:00
yindo closed this issue 2026-02-21 18:07:18 -05:00
yindo commented 2026-02-21 18:07:19 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jul 16, 2024):

The .xlsx files are stuck in the "Queuing" status when using Jina as the Embedding Model in the Dify backend because the rate limit has been reached for the Embedding model API key used. Additionally, it could be due to other issues such as the embedding model not being configured, the model quota being exceeded, or the dataset not being initialized.

Please check the following:

  1. Rate Limit: Ensure that the rate limit for the Embedding model API key has not been reached.
  2. Configuration: Verify that the embedding model is properly configured.
  3. Quota: Check if the model quota has been exceeded.
  4. Dataset Initialization: Ensure that the dataset is initialized.

Supporting evidence:

"Please check if the rate limit has been reached for the Embedding model API key used."
"Error Messages: provider_not_initialize: Embedding model not configured, provider_quota_exceeded: Model quota exceeded, dataset_not_initialized: Dataset not initialized." [1][2].

To continue talking to Dosu, mention @dosu.

@dosubot[bot] commented on GitHub (Jul 16, 2024): <!-- Answer --> The .xlsx files are stuck in the "Queuing" status when using Jina as the Embedding Model in the Dify backend because the rate limit has been reached for the Embedding model API key used. Additionally, it could be due to other issues such as the embedding model not being configured, the model quota being exceeded, or the dataset not being initialized. Please check the following: 1. **Rate Limit**: Ensure that the rate limit for the Embedding model API key has not been reached. 2. **Configuration**: Verify that the embedding model is properly configured. 3. **Quota**: Check if the model quota has been exceeded. 4. **Dataset Initialization**: Ensure that the dataset is initialized. Supporting evidence: > "Please check if the rate limit has been reached for the Embedding model API key used." > "Error Messages: `provider_not_initialize`: Embedding model not configured, `provider_quota_exceeded`: Model quota exceeded, `dataset_not_initialized`: Dataset not initialized." <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/guides/application-orchestrate/llms-use-faq.md)</sup><sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/en/guides/knowledge-base/maintain-dataset-via-api.md)</sup>. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
yindo commented 2026-02-21 18:07:19 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jul 16, 2024):

Link https://github.com/langgenius/dify/issues/6322

@crazywoola commented on GitHub (Jul 16, 2024): Link https://github.com/langgenius/dify/issues/6322
yindo commented 2026-02-21 18:07:19 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jul 16, 2024):

Fixed, our storage is full, we have cleaned some old data to make sure things going well.

@crazywoola commented on GitHub (Jul 16, 2024): Fixed, our storage is full, we have cleaned some old data to make sure things going well.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#4630
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?