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

Enhance the status check api #12794

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

Originally created by @hemin110 on GitHub (Apr 11, 2025).

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.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

For creating knowledge bases, adding new documents, and inserting fragments through the API, there should be corresponding interfaces to query the status. Otherwise, a slight increase in the pressure of API calls may cause Dify to become unresponsive.
The interface for checking the document embedding status in version 1.1.3 returns a 404 error. Please fix it.

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @hemin110 on GitHub (Apr 11, 2025). ### Self Checks - [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] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:) - [x] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. For creating knowledge bases, adding new documents, and inserting fragments through the API, there should be corresponding interfaces to query the status. Otherwise, a slight increase in the pressure of API calls may cause Dify to become unresponsive. The interface for checking the document embedding status in version 1.1.3 returns a 404 error. Please fix it. ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 💪 enhancementgood first issue labels 2026-02-21 19:09:04 -05:00
yindo closed this issue 2026-02-21 19:09:05 -05:00
yindo commented 2026-02-21 19:09:05 -05:00
Author
Owner
Copy Link
Copy Source

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

Are you suggesting you need a index-status endpoint to check the existing task status?

@crazywoola commented on GitHub (Apr 11, 2025): Are you suggesting you need a index-status endpoint to check the existing task status?
yindo commented 2026-02-21 19:09:05 -05:00
Author
Owner
Copy Link
Copy Source

@hemin110 commented on GitHub (Apr 11, 2025):

yeah! 
Support status detection for document creation and status detection for adding document fragments.

分享

------------------ 原始邮件 ------------------
发件人: @.>;
发送时间: 2025年4月11日(星期五) 下午3:36
收件人: @.>;
抄送: @.>; @.>;
主题: Re: [langgenius/dify] Enhance the status check api (Issue #17860)

Are you suggesting you need a index-status endpoint to check the existing task status?

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>
crazywoola left a comment (langgenius/dify#17860)

Are you suggesting you need a index-status endpoint to check the existing task status?

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

@hemin110 commented on GitHub (Apr 11, 2025): yeah!  Support status detection for document creation and status detection for adding document fragments. 分享 ------------------ 原始邮件 ------------------ 发件人: ***@***.***>; 发送时间: 2025年4月11日(星期五) 下午3:36 收件人: ***@***.***>; 抄送: ***@***.***>; ***@***.***>; 主题: Re: [langgenius/dify] Enhance the status check api (Issue #17860) Are you suggesting you need a index-status endpoint to check the existing task status? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***> crazywoola left a comment (langgenius/dify#17860) Are you suggesting you need a index-status endpoint to check the existing task status? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>
yindo commented 2026-02-21 19:09:05 -05:00
Author
Owner
Copy Link
Copy Source

@ZombieBlue commented on GitHub (Apr 14, 2025):

hi，you say the interface for checking the document embedding status return 404，I have try it， it works. Maybe you pass the document ID into batch param, the batch's value is timestamp-like str.
curl --location --request GET 'http://127.0.0.1:5001/v1/datasets/f70e9570-2eeb-4e31-93c5-e2197929bf52/documents/20250414082910430988/indexing-status' --header 'Authorization: Bearer dataset-xxxx' { "data": [ { "id": "0558117e-2340-45fd-94e7-9dea9b08d3e5", "indexing_status": "waiting", "processing_started_at": null, "parsing_completed_at": null, "cleaning_completed_at": null, "splitting_completed_at": null, "completed_at": null, "paused_at": null, "error": null, "stopped_at": null, "completed_segments": 0, "total_segments": 0 } ] }
and i use the document-id as the batch param at first time, too . because it easy to be found in request URL.

curl --location --request GET 'http://127.0.0.1:5001/v1/datasets/f70e9570-2eeb-4e31-93c5-e2197929bf52/documents/8eb4fc3a-d5b7-41db-a54c-0dfd208e8732/indexing-status' --header 'Authorization: Bearer dataset-****' { "code": "not_found", "message": "Documents not found.", "status": 404 }

but，i can't find an service-api return the document's batch value from the api doc.

if user can only upload one file when upload file info dataset, the batch's values are diff in the database,

Image

why the '/datasets/uuid:dataset_id/documents/string:batch/indexing-status' API use the for loop?

Image

@ZombieBlue commented on GitHub (Apr 14, 2025): hi，you say the interface for checking the document embedding status return 404，I have try it， it works. Maybe you pass the document ID into batch param, the batch's value is timestamp-like str. `curl --location --request GET 'http://127.0.0.1:5001/v1/datasets/f70e9570-2eeb-4e31-93c5-e2197929bf52/documents/20250414082910430988/indexing-status' --header 'Authorization: Bearer dataset-xxxx' { "data": [ { "id": "0558117e-2340-45fd-94e7-9dea9b08d3e5", "indexing_status": "waiting", "processing_started_at": null, "parsing_completed_at": null, "cleaning_completed_at": null, "splitting_completed_at": null, "completed_at": null, "paused_at": null, "error": null, "stopped_at": null, "completed_segments": 0, "total_segments": 0 } ] } ` and i use the document-id as the batch param at first time, too . because it easy to be found in request URL. ` curl --location --request GET 'http://127.0.0.1:5001/v1/datasets/f70e9570-2eeb-4e31-93c5-e2197929bf52/documents/8eb4fc3a-d5b7-41db-a54c-0dfd208e8732/indexing-status' --header 'Authorization: Bearer dataset-****' { "code": "not_found", "message": "Documents not found.", "status": 404 }` but，i can't find an service-api return the document's batch value from the api doc. if user can only upload one file when upload file info dataset, the batch's values are diff in the database, ![Image](https://github.com/user-attachments/assets/e4659ef0-0e23-49d1-983b-b2f23ad0dab4) why the '/datasets/<uuid:dataset_id>/documents/<string:batch>/indexing-status' API use the for loop? ![Image](https://github.com/user-attachments/assets/b5f6ab47-bef9-493f-affa-cddfca13a600)
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 good first issue 💪 enhancement
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#12794
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?