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

Severe Lag When Editing Flows With 50+ Nodes #20558

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

Originally created by @agentdaddy on GitHub (Nov 25, 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.0

Cloud or Self Hosted

Cloud

Steps to reproduce

I'm experiencing significant lag with my flow that contains 50+ nodes. This started about 3–4 days ago — previously everything ran smoothly. Now it takes me 5x longer to work on the same tasks, and even opening a single node can take anywhere from a few seconds to a few minutes.

Image

My internet connection shouldn't be the issue (I'm on a 600 Mbps Wi-Fi connection).

✔️ Expected Behavior

  • The flow with 50+ nodes should load smoothly and respond quickly.
  • Opening or editing individual nodes should take less than a second or only a few seconds.
  • Overall performance should be consistent with how it worked previously.

❌ Actual Behavior

  • Over the last 3–4 days, the flow has become extremely laggy.
  • Actions that used to be instant now take 5x longer.
  • Opening a single node often takes several seconds to minutes.
  • The slowdown is constant, despite having a stable high-speed (600 Mbps) internet connection.
Originally created by @agentdaddy on GitHub (Nov 25, 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.0 ### Cloud or Self Hosted Cloud ### Steps to reproduce I'm experiencing significant lag with my flow that contains 50+ nodes. This started about 3–4 days ago — previously everything ran smoothly. Now it takes me 5x longer to work on the same tasks, and even opening a single node can take anywhere from a few seconds to a few minutes. <img width="1853" height="617" alt="Image" src="https://github.com/user-attachments/assets/fbed57a1-2fc7-46a9-a0ca-9c93ae3ea262" /> My internet connection shouldn't be the issue (I'm on a 600 Mbps Wi-Fi connection). ### ✔️ Expected Behavior - The flow with 50+ nodes should load smoothly and respond quickly. - Opening or editing individual nodes should take less than a second or only a few seconds. - Overall performance should be consistent with how it worked previously. ### ❌ Actual Behavior - Over the last 3–4 days, the flow has become extremely laggy. - Actions that used to be instant now take 5x longer. - Opening a single node often takes several seconds to minutes. - The slowdown is constant, despite having a stable high-speed (600 Mbps) internet connection.
yindo closed this issue 2026-02-21 20:07:56 -05:00
yindo commented 2026-02-21 20:07:57 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Nov 25, 2025):

There have been several recent frontend changes to Dify's workflow editor that coincide with the onset of severe lag for flows with 50+ nodes. Notably, PRs merged between Nov 20–25 modified workflow canvas pan/scroll behavior, node control logic, and node rendering, which may have introduced performance regressions for large flows (PR #27981, PR #28591, PR #28250, PR #28248). The workflow editor uses ReactFlow and the ELK layout engine, which can be computationally expensive when handling many nodes, especially if layout recalculations or deep cloning are triggered frequently (workflow-init.ts, elk-layout.ts).

To help diagnose and potentially mitigate the issue, I recommend:

  • Use browser dev tools (Performance tab) to profile CPU and memory usage while opening/editing nodes. Look for excessive re-renders, long scripting/layout times, or large memory spikes.
  • Check if disabling auto-layout or reducing the frequency of draft syncs improves responsiveness.
  • If possible, test with a smaller flow to confirm the issue scales with node count.
  • Share any relevant browser/network traces or error logs with maintainers to help pinpoint the bottleneck.

The timing and scope of these frontend merges strongly suggest a regression affecting large flows. If you need to work around the issue urgently, you might consider temporarily reverting to a previous frontend build before Nov 20, or limiting flow complexity until a fix is released.

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 (Nov 25, 2025): <!-- Answer --> There have been several recent frontend changes to Dify's workflow editor that coincide with the onset of severe lag for flows with 50+ nodes. Notably, PRs merged between Nov 20–25 modified workflow canvas pan/scroll behavior, node control logic, and node rendering, which may have introduced performance regressions for large flows ([PR #27981](https://github.com/langgenius/dify/pull/27981), [PR #28591](https://github.com/langgenius/dify/pull/28591), [PR #28250](https://github.com/langgenius/dify/pull/28250), [PR #28248](https://github.com/langgenius/dify/pull/28248)). The workflow editor uses ReactFlow and the ELK layout engine, which can be computationally expensive when handling many nodes, especially if layout recalculations or deep cloning are triggered frequently ([workflow-init.ts](https://github.com/langgenius/dify/blob/0f521b26aeb03e9f584f4b71a61e37fb709bf601/web/app/components/workflow/utils/workflow-init.ts#L41-L314), [elk-layout.ts](https://github.com/langgenius/dify/blob/0f521b26aeb03e9f584f4b71a61e37fb709bf601/web/app/components/workflow/utils/elk-layout.ts#L23-L529)). To help diagnose and potentially mitigate the issue, I recommend: - Use browser dev tools (Performance tab) to profile CPU and memory usage while opening/editing nodes. Look for excessive re-renders, long scripting/layout times, or large memory spikes. - Check if disabling auto-layout or reducing the frequency of draft syncs improves responsiveness. - If possible, test with a smaller flow to confirm the issue scales with node count. - Share any relevant browser/network traces or error logs with maintainers to help pinpoint the bottleneck. The timing and scope of these frontend merges strongly suggest a regression affecting large flows. If you need to work around the issue urgently, you might consider temporarily reverting to a previous frontend build before Nov 20, or limiting flow complexity until a fix is released. <!-- 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/ed50999d-5fef-43ec-aebf-9ee2573aa535?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/ed50999d-5fef-43ec-aebf-9ee2573aa535?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/ed50999d-5fef-43ec-aebf-9ee2573aa535?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/ed50999d-5fef-43ec-aebf-9ee2573aa535?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ed50999d-5fef-43ec-aebf-9ee2573aa535?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/ed50999d-5fef-43ec-aebf-9ee2573aa535?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ed50999d-5fef-43ec-aebf-9ee2573aa535?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=There%20have%20been%20several%20recent%20frontend%20changes%20to%20Dify%27s%20workflow%20editor%20that%20coincide%20with%20the%20onset%20of%20severe%20lag%20for%20flows%20with%2050%2B%20nodes.%20Notably%2C%20PRs%20merged%20between%20Nov%2020%E2%80%9325%20modified%20workflow%20canvas%20pan/scroll%20behavior%2C%20node%20control%20logic%2C%20and%20node%20rendering%2C%20which%20may%20have%20introduced%20performance%20regressions%20for%20large%20flows%20%28%5BPR%20%2327981%5D%28https%3A//github.com/langgenius/dify/pull/27981%29%2C%20%5BPR%20%2328591%5D%28https%3A//github.com/langgenius/dify/pull/28591%29%2C%20%5BPR%20%2328250%5D%28https%3A//github.com/langgenius/dify/pull/28250%29%2C%20%5BPR%20%2328248%5D%28https%3A//github.com/langgenius/dify/pull/28248%29%29.%20The%20workflow%20editor%20uses%20ReactFlow%20and%20the%20ELK%20layout%20engine%2C%20which%20can%20be%20computationally%20expensive%20when%20handling%20many%20nodes%2C%20especially%20if%20layout%20recalculations%20or%20deep%20cloning%20are%20triggered%20frequently%20%28%5Bworkflow-init.ts%5D%28https%3A//github.com/langgenius/dify/blob/0f521b26aeb03e9f584f4b71a61e37fb709bf601/web/app/components/workflow/utils/workflow-init.ts%23L41-L314%29%2C%20%5Belk-layout.ts%5D%28https%3A//github.com/langgenius/dify/blob/0f521b26aeb03e9f584f4b71a61e37fb709bf601/web/app/components/workflow/utils/elk-layout.ts%23L23-L529%29%29.%0A%0ATo%20help%20diagnose%20and%20potentially%20mitigate%20the%20issue%2C%20I%20recommend%3A%0A%0A-%20Use%20browser%20dev%20tools%20%28Performance%20tab%29%20to%20profile%20CPU%20and%20memory%20usage%20while%20opening/editing%20nodes.%20Look%20for%20excessive%20re-renders%2C%20long%20scripting/layout%20times%2C%20or%20large%20memory%20spikes.%0A-%20Check%20if%20disabling%20auto-layout%20or%20reducing%20the%20frequency%20of%20draft%20syncs%20improves%20responsiveness.%0A-%20If%20possible%2C%20test%20with%20a%20smaller%20flow%20to%20confirm%20the%20issue%20scales%20with%20node%20count.%0A-%20Share%20any%20relevant%20browser/network%20traces%20or%20error%20logs%20with%20maintainers%20to%20help%20pinpoint%20the%20bottleneck.%0A%0AThe%20timing%20and%20scope%20of%20these%20frontend%20merges%20strongly%20suggest%20a%20regression%20affecting%20large%20flows.%20If%20you%20need%20to%20work%20around%20the%20issue%20urgently%2C%20you%20might%20consider%20temporarily%20reverting%20to%20a%20previous%20frontend%20build%20before%20Nov%2020%2C%20or%20limiting%20flow%20complexity%20until%20a%20fix%20is%20released.)&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/28672)
yindo commented 2026-02-21 20:07:57 -05:00
Author
Owner
Copy Link
Copy Source

@homeyone commented on GitHub (Nov 25, 2025):

Indeed, I have experienced the same problem. Sometimes, even when modifying the prompts, a page error occurs, causing the modification to fail. I look forward to the new version fixing this issue.

@homeyone commented on GitHub (Nov 25, 2025): Indeed, I have experienced the same problem. Sometimes, even when modifying the prompts, a page error occurs, causing the modification to fail. I look forward to the new version fixing this issue.
yindo commented 2026-02-21 20:07:57 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Nov 25, 2025):

Duplicated https://github.com/langgenius/dify/issues/28245
Fixed in #28591

@crazywoola commented on GitHub (Nov 25, 2025): Duplicated https://github.com/langgenius/dify/issues/28245 Fixed in [#28591](https://github.com/langgenius/dify/pull/28591)
yindo commented 2026-02-21 20:07:57 -05:00
Author
Owner
Copy Link
Copy Source

@agentdaddy commented on GitHub (Nov 25, 2025):

Duplicated #28245 Fixed in #28591

I don't see it fix on my end. I'm using cloud @crazywoola

@agentdaddy commented on GitHub (Nov 25, 2025): > Duplicated [#28245](https://github.com/langgenius/dify/issues/28245) Fixed in [#28591](https://github.com/langgenius/dify/pull/28591) I don't see it fix on my end. I'm using cloud @crazywoola
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
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#20558
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?