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

Application error: a client-side exception has occurred while loading xxxx (see the browser console for more information) #13325

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

Originally created by @doonygit on GitHub (Apr 24, 2025).

Self Checks

  • 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 (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.2.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When using the Chartflow workflow, if a large number of workflow nodes and branches are created and a certain node at the front is deleted at this time, this error will occur.
The restoration is impossible. The function of restoring historical versions can only be operated in the "Edit" interface. It is necessary to see if it is possible to provide the function of restoring history on the panel page. Otherwise, this abnormal workflow cannot be restored.

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @doonygit on GitHub (Apr 24, 2025). ### Self Checks - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [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. ### Dify version 1.2.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce When using the Chartflow workflow, if a large number of workflow nodes and branches are created and a certain node at the front is deleted at this time, this error will occur. The restoration is impossible. The function of restoring historical versions can only be operated in the "Edit" interface. It is necessary to see if it is possible to provide the function of restoring history on the panel page. Otherwise, this abnormal workflow cannot be restored. ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 🐞 bug label 2026-02-21 19:11:39 -05:00
yindo closed this issue 2026-02-21 19:11:39 -05:00
yindo commented 2026-02-21 19:11:39 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Apr 24, 2025):

Hello @doonygit! 👋 I'm Dosu, your friendly bot here to help with bugs, answer questions, and assist you in becoming a contributor. I'm here while you wait for a human maintainer. Let’s tackle this together! 😊

In the Dify community edition, there is a known limitation regarding workflows with a large number of nodes and branches. You can manually adjust the MAX_TREE_DEPTH limit for single branch depth in web/app/components/workflow/constants.ts. The default value is 50, and excessively deep branches may affect performance in self-hosted scenarios [1].

Regarding the restoration of historical versions, Dify provides a version management interface that allows users to roll back to specific past versions of workflows. This feature is accessible in the "Edit" interface, where you can select a previous version to restore. However, it seems that the restoration functionality is not available directly on the panel page, which might be causing the issue you're experiencing [2].

To address the client-side exception, you might want to check the browser console for more specific error messages that could help in diagnosing the issue further. If the problem persists, consider reviewing the workflow's complexity and structure to ensure it aligns with the current system limitations.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot[bot] commented on GitHub (Apr 24, 2025): <!-- Greeting --> Hello @doonygit! 👋 I'm [Dosu](https://dosu.dev), your friendly bot here to help with bugs, answer questions, and assist you in becoming a contributor. I'm here while you wait for a human maintainer. Let’s tackle this together! 😊 <!-- Answer --> In the Dify community edition, there is a known limitation regarding workflows with a large number of nodes and branches. You can manually adjust the `MAX_TREE_DEPTH` limit for single branch depth in `web/app/components/workflow/constants.ts`. The default value is 50, and excessively deep branches may affect performance in self-hosted scenarios <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/getting-started/install-self-hosted/faqs.md)</sup>. Regarding the restoration of historical versions, Dify provides a version management interface that allows users to roll back to specific past versions of workflows. This feature is accessible in the "Edit" interface, where you can select a previous version to restore. However, it seems that the restoration functionality is not available directly on the panel page, which might be causing the issue you're experiencing <sup>[[2]](https://github.com/langgenius/dify-docs/blob/main/en/guides/management/version-control.md)</sup>. To address the client-side exception, you might want to check the browser console for more specific error messages that could help in diagnosing the issue further. If the problem persists, consider reviewing the workflow's complexity and structure to ensure it aligns with the current system limitations. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/96303bea-5f88-4e86-83e3-63bd9b81e6a6?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/96303bea-5f88-4e86-83e3-63bd9b81e6a6?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/96303bea-5f88-4e86-83e3-63bd9b81e6a6?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/96303bea-5f88-4e86-83e3-63bd9b81e6a6?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/96303bea-5f88-4e86-83e3-63bd9b81e6a6?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/96303bea-5f88-4e86-83e3-63bd9b81e6a6?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/96303bea-5f88-4e86-83e3-63bd9b81e6a6?feedback_type=other)</sup>
yindo commented 2026-02-21 19:11:40 -05:00
Author
Owner
Copy Link
Copy Source

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

Please try 1.3.0, this has been fixed already.

@crazywoola commented on GitHub (Apr 24, 2025): Please try 1.3.0, this has been fixed already.
yindo commented 2026-02-21 19:11:40 -05:00
Author
Owner
Copy Link
Copy Source

@doonygit commented on GitHub (Apr 24, 2025):

Please try 1.3.0, this has been fixed already.

thanks!

@doonygit commented on GitHub (Apr 24, 2025): > Please try 1.3.0, this has been fixed already. thanks!
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 🐞 bug
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#13325
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?