dify - 💡(How to fix) Fix Document download unavailable via UI and API when Knowledge Pipeline is enabled [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
langgenius/dify#35343Fetched 2026-04-17 08:55:59
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
1
Author
Timeline (top)
labeled ×2commented ×1
RAW_BUFFERClick to expand / collapse

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

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When a Dataset is created and processed using the Knowledge Pipeline feature, documents within that Dataset cannot be downloaded through either the Web Console or the API. This functionality works correctly for standard Datasets created without a pipeline.

  1. Create a new Dataset via the Knowledge Pipeline feature.
  2. Configure and save the pipeline workflow.
  3. Publish the pipeline.
  4. Upload a document to the Dataset and wait for the processing/indexing to complete.
<img width="2559" height="1271" alt="Image" src="https://github.com/user-attachments/assets/e1875d74-dc44-4ab7-9e22-dbd3efb8feba" />

✔️ Expected Behavior

  • The Download button should be visible and functional in the Dify Web Console for processed documents.
  • The document should be successfully downloadable via the official API endpoint: GET /v1/datasets/{dataset_id}/documents/{document_id}/download.

❌ Actual Behavior

  • The Download button is completely missing from the Web UI for Datasets utilizing a Knowledge Pipeline (note: it works as expected for standard Datasets).
  • Calling the API endpoint GET /v1/datasets/{dataset_id}/documents/{document_id}/download returns a 404 Not Found response.
<img width="2559" height="1259" alt="Image" src="https://github.com/user-attachments/assets/b3ab5419-bda8-4a67-9c15-f46673e4bde5" /> <img width="2559" height="1262" alt="Image" src="https://github.com/user-attachments/assets/d506fe07-b897-4b5e-acfc-0e3f66525793" />

extent analysis

TL;DR

The issue can be resolved by investigating and potentially modifying the Knowledge Pipeline configuration to ensure it properly handles document downloads.

Guidance

  • Verify that the Knowledge Pipeline workflow is correctly configured to process and index documents, allowing them to be downloadable.
  • Check the API endpoint GET /v1/datasets/{dataset_id}/documents/{document_id}/download to ensure it is correctly handling requests for datasets created with the Knowledge Pipeline feature.
  • Investigate the differences in how standard datasets and those created with the Knowledge Pipeline are handled, focusing on download functionality.
  • Review the Dify version 1.13.2 documentation and release notes for any known issues or changes related to the Knowledge Pipeline and document download functionality.

Example

No specific code snippet can be provided without more details on the pipeline configuration or the API implementation. However, ensuring that the dataset_id and document_id are correctly passed to the API endpoint is crucial.

Notes

The issue seems to be specific to datasets created using the Knowledge Pipeline feature, suggesting a potential configuration or handling difference in this workflow compared to standard datasets.

Recommendation

Apply a workaround by reviewing and adjusting the Knowledge Pipeline configuration to align with the requirements for downloadable documents, as the root cause appears to be related to how the pipeline processes datasets.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

dify - 💡(How to fix) Fix Document download unavailable via UI and API when Knowledge Pipeline is enabled [1 comments, 2 participants]