[Bug]: RAGFlow cannot save the configuration of the dataset slicing method.

[Casplk]

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).
• Non-english title submitions will be closed directly ( 非英文标题的提交将会被直接关闭 ) (Language Policy).
• Please do not modify this template :) and fill in all the required fields.

RAGFlow workspace code commit ID

null

RAGFlow image version

v0.20.4

Other environment information

Actual behavior

When configuring different slicing methods for datasets in RAGFlow, I found that this configuration scheme cannot be saved. In fact, none of the content on this page can be saved, while all other configurations can be saved.

Expected behavior

No response

Steps to reproduce

Dataset -> Configuration -> Slicing Method -> Save

Additional information

No response

[dosubot]

Hi @Casplk! I'm Dosu and I’m helping the ragflow team.

There have been recent changes to the dataset configuration UI and saving logic in RAGFlow, especially around the slicing method ("chunk method") form. The save button logic was refactored into a separate component for permission control, and layout fixes were made to ensure the Save button is visible and functional on all screens (PR #9639, PR #9803). These changes could impact saving behavior for the slicing method configuration.

If saving works for other configuration tabs but not for slicing method, it may be due to how the form values are handled or validated in the frontend, or how the backend processes the slicing method data. No explicit bug fix for this specific issue was found, but the recent UI and permission changes are the most likely cause.

If you see no error message, try checking browser console logs or network requests for clues. If you are on v0.20.4 and still cannot save, you may want to test with the latest patch or review permission settings, as the SavingButton now controls access to saving actions. For more details on the recent changes, see PR #9803 and PR #9639.

To reply, just mention @dosu.

---

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

[Casplk]

I found that the cause of the bug is an issue with library function calls. Line 88 of the chunk-method-form.tsx file: the code let beValid = await form.formControl.trigger(); is modified to let beValid = await form.trigger();, after which it can execute normally.

[dosubot]

Great catch! You're absolutely right—react-hook-form's form context provides the trigger() method directly, so using form.trigger() is the correct way to trigger validation. The previous usage of form.formControl.trigger() doesn't work because formControl isn't a property on the form context, which prevents validation and saving from working as expected. Switching to form.trigger() restores the intended behavior and allows the slicing method configuration to be saved normally, matching the official react-hook-form API and the codebase structure. No custom formControl property exists, so the earlier usage was likely just a mix-up with naming patterns elsewhere in the codebase. Thanks for sharing the fix!
Source: chunk-method-form.tsx, saving-button.tsx

To reply, just mention @dosu.

---

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

[KevinHuSh]

Pull the nightly version of docker image.