General Template Knowledge Base Retrieval

[hulongan]

Self Checks

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

Content

When processing the general document knowledge base, the test pipeline can run smoothly, but after uploading the document, it keeps showing that it is in the queue.

[dosubot[bot]]

The most common reason documents stay stuck in the "queued" state is that the Celery worker for the relevant queue (often priority_pipeline) is not running or not configured to listen to that queue. In Docker deployments, this worker is not started by default, so knowledge base pipeline tasks remain unprocessed until you add a worker for that queue. To fix this, update your docker-compose.yaml to include a service like:

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

Then run docker compose up -d to start the new worker. Multiple users have confirmed this resolves the issue of documents being stuck in the queue [source].

Other things to check: make sure all required services (Celery, database, Redis, vector store) are running and healthy, and that your .env file has DEBUG=false and FLASH_DEBUG=false (setting these to true can cause uploads to get stuck) [source]. If you’re not on the latest Dify release, consider upgrading, as recent versions include fixes for queue management and document status transitions.

If the problem persists, check worker logs for errors, ensure your vector store isn’t in read-only mode, and confirm there are no firewall or resource issues.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}