langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-24 22:11:36 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Bug: add specific plugin tools in workflow report error: "Application error: a client-side exception has occurred while loading..." #15764

New Issue
Closed
opened 2026-02-21 19:23:14 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 19:23:14 -05:00
Owner
Copy Link
Copy Source

Originally created by @weijunjiang123 on GitHub (Jul 30, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

v1.7.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

loading tools of plugin in workflow, click tools card, the front-end white screen report error: "Application error: a client-side exception has occurred while loading 192.168.198.169 (see the browser console for more information)."

Image

✔️ Expected Behavior

load plugin tools and config in workflow

❌ Actual Behavior

after add specific tool in workflow trigger this issue

Image Image

The call stacks point to a compressed obfuscated JS file, and a split operation was performed on null somewhere, resulting in an exception in the page rendering.

Originally created by @weijunjiang123 on GitHub (Jul 30, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [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, 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.7.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce loading tools of plugin in workflow, click tools card, the front-end white screen report error: "Application error: a client-side exception has occurred while loading 192.168.198.169 (see the browser console for more information)." <img width="870" height="500" alt="Image" src="https://github.com/user-attachments/assets/389a7b55-0685-4a0a-908b-9b1680a23878" /> ### ✔️ Expected Behavior load plugin tools and config in workflow ### ❌ Actual Behavior after add specific tool in workflow trigger this issue <img width="860" height="468" alt="Image" src="https://github.com/user-attachments/assets/3e10046f-20c6-407f-8829-397f0e0f25d9" /> <img width="664" height="750" alt="Image" src="https://github.com/user-attachments/assets/c3b85990-cacf-4301-947a-0fad75243b2f" /> The call stacks point to a compressed obfuscated JS file, and a split operation was performed on null somewhere, resulting in an exception in the page rendering.
yindo added the 🐞 buggood first issue labels 2026-02-21 19:23:14 -05:00
yindo closed this issue 2026-02-21 19:23:14 -05:00
yindo commented 2026-02-21 19:23:14 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jul 30, 2025):

This error is a known issue in Dify, especially with plugin tools in workflows, and is usually caused by missing or malformed data leading to unguarded string operations in the frontend code—like calling .split() on a null or undefined value. In your version (v1.7.1), the most likely culprit is the lack of null checks in components such as switch-plugin-version.tsx and use-single-run-form-params.ts, where identifiers or values from plugin configs are assumed to always be present and valid. If a plugin's metadata or configuration is missing required fields, this triggers the crash you’re seeing example.

To mitigate or debug this:

  • Check that all plugin metadata (like uniqueIdentifier, meta, and minimum_dify_version) is present and well-formed in your plugins example.
  • If you build your own Docker images, try rebuilding or switching to the official frontend image to rule out packaging errors.
  • If you have custom plugins, validate their manifest and config fields.
  • In the code, add defensive checks before any .split() or similar string operations, e.g. if (uniqueIdentifier) { ... uniqueIdentifier.split(':') ... }.

If the issue persists, capturing the exact plugin/tool and the full browser console stack trace will help pinpoint the root cause for a permanent fix. This class of bug has been reported as a regression since v1.6.0 and is being tracked in several issues see related see related.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Jul 30, 2025): <!-- Answer --> This error is a known issue in Dify, especially with plugin tools in workflows, and is usually caused by missing or malformed data leading to unguarded string operations in the frontend code—like calling `.split()` on a null or undefined value. In your version (v1.7.1), the most likely culprit is the lack of null checks in components such as `switch-plugin-version.tsx` and `use-single-run-form-params.ts`, where identifiers or values from plugin configs are assumed to always be present and valid. If a plugin's metadata or configuration is missing required fields, this triggers the crash you’re seeing [example](https://github.com/langgenius/dify/issues/23003). To mitigate or debug this: - Check that all plugin metadata (like `uniqueIdentifier`, `meta`, and `minimum_dify_version`) is present and well-formed in your plugins [example](https://github.com/langgenius/dify/issues/18423). - If you build your own Docker images, try rebuilding or switching to the official frontend image to rule out packaging errors. - If you have custom plugins, validate their manifest and config fields. - In the code, add defensive checks before any `.split()` or similar string operations, e.g. `if (uniqueIdentifier) { ... uniqueIdentifier.split(':') ... }`. If the issue persists, capturing the exact plugin/tool and the full browser console stack trace will help pinpoint the root cause for a permanent fix. This class of bug has been reported as a regression since v1.6.0 and is being tracked in several issues [see related](https://github.com/langgenius/dify/issues/23003) [see related](https://github.com/langgenius/dify/issues/21219). <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/a9cde806-0d6b-4bf6-a539-37fdb6013fab?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/a9cde806-0d6b-4bf6-a539-37fdb6013fab?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/a9cde806-0d6b-4bf6-a539-37fdb6013fab?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/a9cde806-0d6b-4bf6-a539-37fdb6013fab?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/a9cde806-0d6b-4bf6-a539-37fdb6013fab?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/a9cde806-0d6b-4bf6-a539-37fdb6013fab?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/a9cde806-0d6b-4bf6-a539-37fdb6013fab?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/23154)
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 🐞 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#15764
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?