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

Client-side exception when clicking Test run on workflow edit (Minified React error #185) #21032

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

Originally created by @erbanku on GitHub (Dec 14, 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

1.10.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

  1. Go to workflow edit page
  2. Click 'Test run'
  3. Observe the client-side exception and error message
Error screenshot

Console log:

Uncaught Error: Minified React error #185; visit https://react.dev/errors/185 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at t7 (203ec9d0-c87e5929e66301d9.js:1:30827)
    at t5 (203ec9d0-c87e5929e66301d9.js:1:30399)
    at ak (203ec9d0-c87e5929e66301d9.js:1:55888)
    at ay (203ec9d0-c87e5929e66301d9.js:1:55714)
    at o1 (203ec9d0-c87e5929e66301d9.js:1:88958)
    at uE (203ec9d0-c87e5929e66301d9.js:1:104850)
    at ux (203ec9d0-c87e5929e66301d9.js:1:104734)
    at uE (203ec9d0-c87e5929e66301d9.js:1:104895)
    at ux (203ec9d0-c87e5929e66301d9.js:1:104734)
    at uE (203ec9d0-c87e5929e66301d9.js:1:104895)
    at ux (203ec9d0-c87e5929e66301d9.js:1:104734)
    at uE (203ec9d0-c87e5929e66301d9.js:1:104895)
    at ux (203ec9d0-c87e5929e66301d9.js:1:104734)
    at uE (203ec9d0-c87e5929e66301d9.js:1:104830)
    at ux (203ec9d0-c87e5929e66301d9.js:1:104734)
    at uE (203ec9d0-c87e5929e66301d9.js:1:104830)
    at ux (203ec9d0-c87e5929e66301d9.js:1:104734)
    ...

✔️ Expected Behavior

The test run should execute or show a clear message.
No React errors should occur.

❌ Actual Behavior

A client-side exception occurs, preventing workflow testing. See attached screenshot and console error.

Originally created by @erbanku on GitHub (Dec 14, 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 1.10.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 1. Go to workflow edit page 2. Click 'Test run' 3. Observe the client-side exception and error message <img alt="Error screenshot" width="1564" src="https://github.com/user-attachments/assets/9b262e33-e1dd-4f02-904c-19fc0c4e28c2" /> Console log: ``` Uncaught Error: Minified React error #185; visit https://react.dev/errors/185 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. at t7 (203ec9d0-c87e5929e66301d9.js:1:30827) at t5 (203ec9d0-c87e5929e66301d9.js:1:30399) at ak (203ec9d0-c87e5929e66301d9.js:1:55888) at ay (203ec9d0-c87e5929e66301d9.js:1:55714) at o1 (203ec9d0-c87e5929e66301d9.js:1:88958) at uE (203ec9d0-c87e5929e66301d9.js:1:104850) at ux (203ec9d0-c87e5929e66301d9.js:1:104734) at uE (203ec9d0-c87e5929e66301d9.js:1:104895) at ux (203ec9d0-c87e5929e66301d9.js:1:104734) at uE (203ec9d0-c87e5929e66301d9.js:1:104895) at ux (203ec9d0-c87e5929e66301d9.js:1:104734) at uE (203ec9d0-c87e5929e66301d9.js:1:104895) at ux (203ec9d0-c87e5929e66301d9.js:1:104734) at uE (203ec9d0-c87e5929e66301d9.js:1:104830) at ux (203ec9d0-c87e5929e66301d9.js:1:104734) at uE (203ec9d0-c87e5929e66301d9.js:1:104830) at ux (203ec9d0-c87e5929e66301d9.js:1:104734) ... ``` ### ✔️ Expected Behavior The test run should execute or show a clear message. No React errors should occur. ### ❌ Actual Behavior A client-side exception occurs, preventing workflow testing. See attached screenshot and console error.
yindo added the 🐞 bug label 2026-02-21 20:10:21 -05:00
yindo closed this issue 2026-02-21 20:10:21 -05:00
yindo commented 2026-02-21 20:10:21 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 14, 2025):

The React error (#185) you’re seeing when clicking "Test run" is likely caused by a frontend rendering or state management issue—often due to missing or malformed workflow node data, or an unexpected state in the workflow test run dropdown logic. Recent changes to the test run feature replaced mock data with dynamic options based on actual workflow nodes, which can surface edge cases if the workflow graph is incomplete or contains unexpected nodes. Defensive coding (null checks, fallback UI) is recommended in these components, especially if you have custom modifications or unusual workflow setups [example].

Here’s what you can try:

  • Make sure your frontend and backend containers are running the same Dify version and that your frontend Docker image is up to date, as version mismatches can cause similar errors [example].
  • Check your workflow for missing or misconfigured nodes, especially triggers (Start, Schedule, Webhook, Plugin). Try simplifying the workflow to a minimal setup to see if the error persists.
  • If you have custom workflow nodes or have edited the workflow JSON directly, ensure all required fields are present and valid.
  • If you’re comfortable with code, consider running the frontend in development mode (non-minified React) to get the full error message and stack trace, which will pinpoint the exact cause.
  • Upgrading to the latest Dify version may help, as recent releases have improved error handling and validation in workflow components [PR #24320].

If the error persists, capturing the full error message in a dev build or sharing more details about your workflow structure will help narrow it down.

To reply, just mention @dosu.

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

Chat with Dosu Open in Cursor Join Discord Share on X

@dosubot[bot] commented on GitHub (Dec 14, 2025): <!-- Answer --> The React error (#185) you’re seeing when clicking "Test run" is likely caused by a frontend rendering or state management issue—often due to missing or malformed workflow node data, or an unexpected state in the workflow test run dropdown logic. Recent changes to the test run feature replaced mock data with dynamic options based on actual workflow nodes, which can surface edge cases if the workflow graph is incomplete or contains unexpected nodes. Defensive coding (null checks, fallback UI) is recommended in these components, especially if you have custom modifications or unusual workflow setups [[example](https://github.com/langgenius/dify/issues/23003)]. Here’s what you can try: - Make sure your frontend and backend containers are running the same Dify version and that your frontend Docker image is up to date, as version mismatches can cause similar errors [[example](https://github.com/langgenius/dify/issues/12532)]. - Check your workflow for missing or misconfigured nodes, especially triggers (Start, Schedule, Webhook, Plugin). Try simplifying the workflow to a minimal setup to see if the error persists. - If you have custom workflow nodes or have edited the workflow JSON directly, ensure all required fields are present and valid. - If you’re comfortable with code, consider running the frontend in development mode (non-minified React) to get the full error message and stack trace, which will pinpoint the exact cause. - Upgrading to the latest Dify version may help, as recent releases have improved error handling and validation in workflow components [[PR #24320](https://github.com/langgenius/dify/pull/24320)]. If the error persists, capturing the full error message in a dev build or sharing more details about your workflow structure will help narrow it down. <!-- 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/659b1c3a-25d4-435e-a4cd-7f3af9a086e2?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/659b1c3a-25d4-435e-a4cd-7f3af9a086e2?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/659b1c3a-25d4-435e-a4cd-7f3af9a086e2?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/659b1c3a-25d4-435e-a4cd-7f3af9a086e2?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/659b1c3a-25d4-435e-a4cd-7f3af9a086e2?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/659b1c3a-25d4-435e-a4cd-7f3af9a086e2?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/659b1c3a-25d4-435e-a4cd-7f3af9a086e2?feedback_type=other)</sup> [![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Open in Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=The%20React%20error%20%28%23185%29%20you%E2%80%99re%20seeing%20when%20clicking%20%22Test%20run%22%20is%20likely%20caused%20by%20a%20frontend%20rendering%20or%20state%20management%20issue%E2%80%94often%20due%20to%20missing%20or%20malformed%20workflow%20node%20data%2C%20or%20an%20unexpected%20state%20in%20the%20workflow%20test%20run%20dropdown%20logic.%20Recent%20changes%20to%20the%20test%20run%20feature%20replaced%20mock%20data%20with%20dynamic%20options%20based%20on%20actual%20workflow%20nodes%2C%20which%20can%20surface%20edge%20cases%20if%20the%20workflow%20graph%20is%20incomplete%20or%20contains%20unexpected%20nodes.%20Defensive%20coding%20%28null%20checks%2C%20fallback%20UI%29%20is%20recommended%20in%20these%20components%2C%20especially%20if%20you%20have%20custom%20modifications%20or%20unusual%20workflow%20setups%20%5B%5Bexample%5D%28https%3A//github.com/langgenius/dify/issues/23003%29%5D.%0A%0AHere%E2%80%99s%20what%20you%20can%20try%3A%0A-%20Make%20sure%20your%20frontend%20and%20backend%20containers%20are%20running%20the%20same%20Dify%20version%20and%20that%20your%20frontend%20Docker%20image%20is%20up%20to%20date%2C%20as%20version%20mismatches%20can%20cause%20similar%20errors%20%5B%5Bexample%5D%28https%3A//github.com/langgenius/dify/issues/12532%29%5D.%0A-%20Check%20your%20workflow%20for%20missing%20or%20misconfigured%20nodes%2C%20especially%20triggers%20%28Start%2C%20Schedule%2C%20Webhook%2C%20Plugin%29.%20Try%20simplifying%20the%20workflow%20to%20a%20minimal%20setup%20to%20see%20if%20the%20error%20persists.%0A-%20If%20you%20have%20custom%20workflow%20nodes%20or%20have%20edited%20the%20workflow%20JSON%20directly%2C%20ensure%20all%20required%20fields%20are%20present%20and%20valid.%0A-%20If%20you%E2%80%99re%20comfortable%20with%20code%2C%20consider%20running%20the%20frontend%20in%20development%20mode%20%28non-minified%20React%29%20to%20get%20the%20full%20error%20message%20and%20stack%20trace%2C%20which%20will%20pinpoint%20the%20exact%20cause.%0A-%20Upgrading%20to%20the%20latest%20Dify%20version%20may%20help%2C%20as%20recent%20releases%20have%20improved%20error%20handling%20and%20validation%20in%20workflow%20components%20%5B%5BPR%20%2324320%5D%28https%3A//github.com/langgenius/dify/pull/24320%29%5D.%0A%0AIf%20the%20error%20persists%2C%20capturing%20the%20full%20error%20message%20in%20a%20dev%20build%20or%20sharing%20more%20details%20about%20your%20workflow%20structure%20will%20help%20narrow%20it%20down.)&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/29634)
yindo commented 2026-02-21 20:10:21 -05:00
Author
Owner
Copy Link
Copy Source

@AnushkaSarviya commented on GitHub (Dec 14, 2025):

@erbanku Technical analysis

i think the client-side crash is caused by an infinite React state update loop triggered when clicking Test run in the workflow editor.
The error Minified React indicates that one of the components involved in the Test run flow is calling a state setter (setState / useState) in a way that immediately causes a re-render, which then triggers the same update again.
this could be because of
A useEffect that updates state without a dependency array or with a self-referencing dependency
A circular parent child update (e.g., editor state → test runner → editor state)
Derived state recalculated from itself (e.g., useEffect(() => setX(derive(x)), [x]))

Since it only occurs after clicking Test run, the issue is likely in the workflow test-run UI logic (e.g. a useEffect or editor ↔ test runner state sync causing a circular update).

Running the frontend in dev mode should reveal the non-minified error and point to the offending component. This appears to be a frontend regression in v1.10.1.

@AnushkaSarviya commented on GitHub (Dec 14, 2025): @erbanku Technical analysis i think the client-side crash is caused by an infinite React state update loop triggered when clicking Test run in the workflow editor. The error Minified React indicates that one of the components involved in the Test run flow is calling a state setter (setState / useState) in a way that immediately causes a re-render, which then triggers the same update again. this could be because of A useEffect that updates state without a dependency array or with a self-referencing dependency A circular parent child update (e.g., editor state → test runner → editor state) Derived state recalculated from itself (e.g., useEffect(() => setX(derive(x)), [x])) Since it only occurs after clicking Test run, the issue is likely in the workflow test-run UI logic (e.g. a useEffect or editor ↔ test runner state sync causing a circular update). Running the frontend in dev mode should reveal the non-minified error and point to the offending component. This appears to be a frontend regression in v1.10.1.
yindo commented 2026-02-21 20:10:21 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Dec 14, 2025):

This should be fixed in the v1.11.1

@crazywoola commented on GitHub (Dec 14, 2025): This should be fixed in the v1.11.1
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#21032
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?