Failed to add or edit child chunk
Self Checks
- [x] I have read the Contributing Guide and Language Policy.
- [x] This is only for bug report, if you would like to ask a question, please head to Discussions.
- [x] I have searched for existing issues search for existing 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
v1.9.1
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
- add child chunk
- edit child chunk
Although the interface call succeeded and there were no error messages in the logs, the creation or modification of the item failed in the end.
✔️ Expected Behavior
The system should correctly add or edit child chunk.
❌ Actual Behavior
No response
The backend for adding and editing child chunks in Dify relies on several checks and database operations. The API validates dataset, document, segment, and user permissions before calling service methods to create or update child chunks. If any of these checks fail, the operation is skipped and may not raise an error, resulting in a successful UI response but no actual change in the database. There is also no explicit error logging or transaction rollback in the lower-level code, so silent validation failures or logic errors (like mismatched IDs or missing required fields) can cause the issue you described without leaving traces in the logs. Double-check that all required IDs and permissions are correct, and that the dataset and segment exist and are enabled. If possible, try enabling debug logging or inspecting the database directly to confirm whether the child chunk records are being created or updated as expected. For more details, see the backend controller and service logic for child chunk operations here and here.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other
I have the same experience, with the knowledge base created via pipelines. Adding/editing chunks seems to work for existing knowledge bases.
Hi, @leoterry-ulrica. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.
Issue Summary:
- You reported that in version 1.9.1 of the self-hosted Docker setup, adding or editing child chunks appears successful but changes do not persist.
- A contributor suggested that silent validation failures or backend permission checks might cause this without error logs.
- Recommendations included verifying IDs, permissions, dataset status, enabling debug logging, and inspecting the database.
- Another user confirmed similar issues specifically with knowledge bases created via pipelines, while edits on existing knowledge bases worked fine.
- The issue remains unresolved with no confirmed fix or workaround yet.
Next Steps:
- Please let me know if this issue is still relevant with the latest version of Dify by commenting here to keep the discussion open.
- Otherwise, this issue will be automatically closed in 15 days.
Thank you for your understanding and contribution!