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

The knowledge pipeline of Dify 1.9.2 cannot build a knowledge base. #20149

New Issue
Closed
opened 2026-02-21 20:06:03 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 20:06:03 -05:00
Owner
Copy Link
Copy Source

Originally created by @lhxxrds on GitHub (Nov 5, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.9.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

The knowledge pipeline of dify1.9.2 version has been created. Under normal circumstances, the knowledge base cannot be embedded and constructed through the knowledge pipeline, and it keeps showing that it is queuing. What's the problem?

✔️ Expected Behavior

The knowledge pipeline of dify1.9.2 version has been created. Under normal circumstances, the knowledge base cannot be embedded and constructed through the knowledge pipeline, and it keeps showing that it is queuing. What's the problem?

❌ Actual Behavior

The knowledge pipeline of dify1.9.2 version has been created. Under normal circumstances, the knowledge base cannot be embedded and constructed through the knowledge pipeline, and it keeps showing that it is queuing. What's the problem?

Originally created by @lhxxrds on GitHub (Nov 5, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.9.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce The knowledge pipeline of dify1.9.2 version has been created. Under normal circumstances, the knowledge base cannot be embedded and constructed through the knowledge pipeline, and it keeps showing that it is queuing. What's the problem? ### ✔️ Expected Behavior The knowledge pipeline of dify1.9.2 version has been created. Under normal circumstances, the knowledge base cannot be embedded and constructed through the knowledge pipeline, and it keeps showing that it is queuing. What's the problem? ### ❌ Actual Behavior **The knowledge pipeline of dify1.9.2 version has been created. Under normal circumstances, the knowledge base cannot be embedded and constructed through the knowledge pipeline, and it keeps showing that it is queuing. What's the problem?**
yindo added the 🐞 bug🌚 invalid labels 2026-02-21 20:06:03 -05:00
yindo closed this issue 2026-02-21 20:06:04 -05:00
yindo commented 2026-02-21 20:06:04 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 5, 2025):

The knowledge pipeline in Dify 1.9.2 self-hosted Docker often remains queued due to issues with required background services or misconfiguration. Common causes include: the Celery worker not running or not subscribed to the correct queue, Redis not running or not accessible, missing or misconfigured vector database containers (like Weaviate), missing or invalid embedding provider API keys (such as OPENAI_API_KEY), or Python and locale misconfigurations in containers. If any of these are not set up or connected properly, the pipeline will stay in the "queuing" state and never proceed to embedding or building the knowledge base.

To resolve this, check that:

  • The Celery worker is running and connected to Redis, and is subscribed to the pipeline queue.
  • Redis is running and accessible from all containers.
  • The vector database container (e.g., Weaviate) is running and healthy, and the VECTOR_STORE environment variable is set consistently.
  • The embedding provider API key (e.g., OPENAI_API_KEY) is set in your .env file and the API/worker containers are restarted after setting it.
  • Python 3.10 and required libraries are installed in the sandbox container, and locale variables (LANG and LC_ALL) are set to en_US.UTF-8 in all API containers.

Recent updates have improved error handling and embedding process reliability, so consider upgrading if possible. For more details and troubleshooting steps, see this discussion and this recent fix.

Check your container logs for errors related to Celery, Redis, vector DB, or embedding, as these will usually indicate what is blocking the pipeline from progressing.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Nov 5, 2025): <!-- Answer --> The knowledge pipeline in Dify 1.9.2 self-hosted Docker often remains queued due to issues with required background services or misconfiguration. Common causes include: the Celery worker not running or not subscribed to the correct queue, Redis not running or not accessible, missing or misconfigured vector database containers (like Weaviate), missing or invalid embedding provider API keys (such as `OPENAI_API_KEY`), or Python and locale misconfigurations in containers. If any of these are not set up or connected properly, the pipeline will stay in the "queuing" state and never proceed to embedding or building the knowledge base. To resolve this, check that: - The Celery worker is running and connected to Redis, and is subscribed to the `pipeline` queue. - Redis is running and accessible from all containers. - The vector database container (e.g., Weaviate) is running and healthy, and the `VECTOR_STORE` environment variable is set consistently. - The embedding provider API key (e.g., `OPENAI_API_KEY`) is set in your `.env` file and the API/worker containers are restarted after setting it. - Python 3.10 and required libraries are installed in the sandbox container, and locale variables (`LANG` and `LC_ALL`) are set to `en_US.UTF-8` in all API containers. Recent updates have improved error handling and embedding process reliability, so consider upgrading if possible. For more details and troubleshooting steps, see [this discussion](https://github.com/langgenius/dify-docs/issues/397) and [this recent fix](https://github.com/langgenius/dify/pull/26830). Check your container logs for errors related to Celery, Redis, vector DB, or embedding, as these will usually indicate what is blocking the pipeline from progressing. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/298a4e57-25a8-49b1-8280-92972bab208d?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/298a4e57-25a8-49b1-8280-92972bab208d?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/298a4e57-25a8-49b1-8280-92972bab208d?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/298a4e57-25a8-49b1-8280-92972bab208d?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/298a4e57-25a8-49b1-8280-92972bab208d?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/298a4e57-25a8-49b1-8280-92972bab208d?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/298a4e57-25a8-49b1-8280-92972bab208d?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/27859)
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 🌚 invalid 🐞 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#20149
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?