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 retrieval of the knowledge base is empty. #20234

New Issue
Closed
opened 2026-02-21 20:06:24 -05:00 by yindo · 5 comments
yindo commented 2026-02-21 20:06:24 -05:00
Owner
Copy Link
Copy Source

Originally created by @qq749812679 on GitHub (Nov 10, 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 retrieval of the knowledge base is empty.

✔️ Expected Behavior

The retrieval of the knowledge base is not empty.

❌ Actual Behavior

The retrieval of the knowledge base is empty.

Originally created by @qq749812679 on GitHub (Nov 10, 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 retrieval of the knowledge base is empty. ### ✔️ Expected Behavior The retrieval of the knowledge base is not empty. ### ❌ Actual Behavior The retrieval of the knowledge base is empty.
yindo added the 🌚 invalid label 2026-02-21 20:06:24 -05:00
yindo closed this issue 2026-02-21 20:06:24 -05:00
yindo commented 2026-02-21 20:06:24 -05:00
Author
Owner
Copy Link
Copy Source

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

The most common cause for empty knowledge base retrieval in Dify v1.9.2 (self-hosted via Docker) is that the Celery worker for the priority_pipeline queue is not started by default, so knowledgebase pipeline tasks remain stuck and unprocessed. To fix this, add a Celery worker service for the priority_pipeline queue in your docker-compose.yaml or entrypoint.sh:

priority-worker:
  image: langgenius/dify-api:1.9.2
  restart: always
  environment:
    <<: *shared-api-worker-env
    MODE: worker
    CELERY_QUEUES: priority_pipeline
    CELERY_WORKER_AMOUNT: 2
    LOG_LEVEL: INFO
  depends_on:
    db:
      condition: service_healthy
    redis:
      condition: service_started
  volumes:
    - ./volumes/app/storage:/app/api/storage
  networks:
    - ssrf_proxy_network
    - default

After adding this, run docker compose down and then docker compose up -d to restart with the new configuration. This should resolve the issue and allow the knowledge base pipeline to process tasks and enable retrieval. For more details, see this issue.

If retrieval is still empty, check for misconfigurations: make sure your knowledge base is indexed, your retrieval settings match your indexing method (use search_method: keyword_search for "economical" index), and your documents have the correct metadata. Use the "Recall Test" feature to simulate queries and check logs for errors during ingestion or retrieval. More troubleshooting tips are available here and here.

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 10, 2025): <!-- Answer --> The most common cause for empty knowledge base retrieval in Dify v1.9.2 (self-hosted via Docker) is that the Celery worker for the `priority_pipeline` queue is not started by default, so knowledgebase pipeline tasks remain stuck and unprocessed. To fix this, add a Celery worker service for the `priority_pipeline` queue in your `docker-compose.yaml` or `entrypoint.sh`: ```yaml priority-worker: image: langgenius/dify-api:1.9.2 restart: always environment: <<: *shared-api-worker-env MODE: worker CELERY_QUEUES: priority_pipeline CELERY_WORKER_AMOUNT: 2 LOG_LEVEL: INFO depends_on: db: condition: service_healthy redis: condition: service_started volumes: - ./volumes/app/storage:/app/api/storage networks: - ssrf_proxy_network - default ``` After adding this, run `docker compose down` and then `docker compose up -d` to restart with the new configuration. This should resolve the issue and allow the knowledge base pipeline to process tasks and enable retrieval. For more details, see [this issue](https://github.com/langgenius/dify/issues/27419). If retrieval is still empty, check for misconfigurations: make sure your knowledge base is indexed, your retrieval settings match your indexing method (use `search_method: keyword_search` for "economical" index), and your documents have the correct metadata. Use the "Recall Test" feature to simulate queries and check logs for errors during ingestion or retrieval. More troubleshooting tips are available [here](https://github.com/langgenius/dify/issues/16767) and [here](https://github.com/langgenius/dify/issues/25084). <!-- 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/9dab52b2-3465-4d32-8120-804509e04804?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/9dab52b2-3465-4d32-8120-804509e04804?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/9dab52b2-3465-4d32-8120-804509e04804?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/9dab52b2-3465-4d32-8120-804509e04804?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/9dab52b2-3465-4d32-8120-804509e04804?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/9dab52b2-3465-4d32-8120-804509e04804?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/9dab52b2-3465-4d32-8120-804509e04804?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/28043)
yindo commented 2026-02-21 20:06:24 -05:00
Author
Owner
Copy Link
Copy Source

@DavideDelbianco commented on GitHub (Nov 10, 2025):

@crazywoola can you clarify dosu suggestion?

What is the priority_pipeline worker that it suggests ?

@DavideDelbianco commented on GitHub (Nov 10, 2025): @crazywoola can you clarify dosu suggestion? What is the priority_pipeline worker that it suggests ?
yindo commented 2026-02-21 20:06:24 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Nov 10, 2025):

https://github.com/langgenius/dify/blob/20ad5b7ac2cfea42dc0743067eb3536452f60323/api/README.md#L82-L84

For example, in our SaaS environment, we have a queue to proceed all the incoming tasks. There are two types of the queue. Paid users will have their docs get processed by the priority_pipeline while free sandbox plan users will have their docs in the pipeline. @DavideDelbianco

  • priority_pipeline
  • pipeline
@crazywoola commented on GitHub (Nov 10, 2025): https://github.com/langgenius/dify/blob/20ad5b7ac2cfea42dc0743067eb3536452f60323/api/README.md#L82-L84 For example, in our SaaS environment, we have a queue to proceed all the incoming tasks. There are two types of the queue. Paid users will have their docs get processed by the `priority_pipeline` while free sandbox plan users will have their docs in the `pipeline`. @DavideDelbianco - priority_pipeline - pipeline
yindo commented 2026-02-21 20:06:24 -05:00
Author
Owner
Copy Link
Copy Source

@DavideDelbianco commented on GitHub (Nov 11, 2025):

In self hosted the messages go to normal or priority queue? If it's the latter, is dose telling the truth about the queue not being processed?

@DavideDelbianco commented on GitHub (Nov 11, 2025): In self hosted the messages go to normal or priority queue? If it's the latter, is dose telling the truth about the queue not being processed?
yindo commented 2026-02-21 20:06:24 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Nov 11, 2025):

This is related to previous PR https://github.com/langgenius/dify/pull/27554. Some of the tasks are going to the wrong queue.

@crazywoola commented on GitHub (Nov 11, 2025): This is related to previous PR https://github.com/langgenius/dify/pull/27554. Some of the tasks are going to the wrong queue.
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
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#20234
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?