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

Browser Unresponsiveness ("Page Not Responding") During Workflow Execution #19197

New Issue
Closed
opened 2026-02-21 19:56:53 -05:00 by yindo · 0 comments
yindo commented 2026-02-21 19:56:53 -05:00
Owner
Copy Link
Copy Source

Originally created by @boyu-lin on GitHub (Oct 13, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • 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.
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Overview

In a specific workflow within Dify Enterprise, users frequently encounter a "Page Not Responding" dialog in the browser. Although the process appears to complete successfully when the page is refreshed or revisited, attempting to view execution history details results in similar timeout behavior.

Reproduction Conditions

User-side investigation has identified the following conditions under which the issue occurs:

  • The standard "Answer" node (marked in orange) is used to output a table containing input data and calculated results.
  • When the output size exceeds a certain threshold, the browser display freezes.
  • When the workflow is adjusted to bypass the affected nodes (4 instances), the issue no longer occurs.

Suspected Cause

It is suspected that large output data volumes are causing the browser to stall during rendering, leading to the observed unresponsiveness.

Request

We kindly request consideration for improvements to how large output data is handled in the browser. Potential solutions might include:

  • Lazy loading of output content
  • Collapsible table views
  • Asynchronous rendering of execution history details

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @boyu-lin on GitHub (Oct 13, 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] 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] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Tell me about your story. #### Overview In a specific workflow within Dify Enterprise, users frequently encounter a "Page Not Responding" dialog in the browser. Although the process appears to complete successfully when the page is refreshed or revisited, attempting to view execution history details results in similar timeout behavior. #### Reproduction Conditions User-side investigation has identified the following conditions under which the issue occurs: - The standard "Answer" node (marked in orange) is used to output a table containing input data and calculated results. - When the output size exceeds a certain threshold, the browser display freezes. - When the workflow is adjusted to bypass the affected nodes (4 instances), the issue no longer occurs. #### Suspected Cause It is suspected that large output data volumes are causing the browser to stall during rendering, leading to the observed unresponsiveness. #### Request We kindly request consideration for improvements to how large output data is handled in the browser. Potential solutions might include: - Lazy loading of output content - Collapsible table views - Asynchronous rendering of execution history details ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo closed this issue 2026-02-21 19:56:54 -05:00
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#19197
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?