[Bug]: Error while trying to load the Knowledge Base Agent

[meetcharan-practice]

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

NA

RAGFlow image version

ragflow:v0.22.0

Other environment information

Actual behavior

I’m encountering the following errors when loading the Knowledge Base Agent and when accessing the Configuration button.

Expected behavior

No response

Steps to reproduce

Create an Agent and select the Knowledge Base Agent. Check the browser console to view any errors.

Next, click the Configuration button—this will cause the entire screen to go blank.

Additional information

No response

[dosubot]

The errors and blank screen you’re seeing when loading the Knowledge Base Agent and clicking the Configuration button in RAGFlow v0.22.0 are likely caused by frontend issues with the schema visual editor and its use of web workers. Specifically, the UI tries to load jsonWorker.js for background processing, but if the worker URL is misconfigured or the script is missing, this triggers a cascade of JavaScript errors. These errors—along with attempts to access undefined properties in schema-visual-editor.tsx—can crash the UI and result in a blank screen. This is a known issue and is being tracked in the project’s open issues (reference).

The relevant code shows that the Configuration button opens a dialog that relies on the schema visual editor, which in turn depends on web workers for JSON schema editing. If the worker fails to load or the schema state is invalid, the editor will throw errors and the dialog (and sometimes the whole screen) will go blank (reference, reference).

Common causes include: missing or misconfigured web worker scripts, frontend/backend version mismatches, or malformed agent configuration data. You can check your browser console and backend logs for more details, and ensure your deployment includes all required static assets for the frontend. If you’re running a custom or self-hosted build, double-check the worker script paths and bundler configuration.

This issue is actively tracked, so keep an eye on updates or patches in future releases.

To reply, just mention @dosu.

---

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