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

Workflow execution stuck in “Running” state during load testing — requests hang and get terminated after 20 minutes #19234

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

Originally created by @weyuhui110 on GitHub (Oct 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.8.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image Image Image

Description

When performing load testing on the workflow conversation API, some workflow runs get stuck in the “Running” state. After approximately 20 minutes, these executions are automatically stopped by the system.

This issue does not occur under single request conditions — it only appears when concurrency increases (during stress or load tests).

When checking the workflow run history, I noticed that:

Some parallel branches have partially executed nodes.

Subsequent nodes in those branches are never executed.

On the UI, all nodes appear as completed, even though some were never actually run.

There is no clear indication of which node or branch the execution got stuck on.

So effectively, the workflow is partially executed and stuck, but the UI and logs don’t show which node caused the issue.
Steps to Reproduce

Create a workflow with multiple parallel branches/nodes (around 30 concurrent nodes).

Run the workflow through the “workflow conversation API” using a load testing tool (e.g., 100+ concurrent requests).

Observe that some workflow runs remain in “Running” state indefinitely.

Wait ~20 minutes — the system automatically terminates those stuck runs.

Check the workflow run history: you’ll see incomplete execution graphs (some branches not started).

✔️ Expected Behavior

All workflow executions should complete successfully or fail with a clear error message showing which node or branch caused the problem.

❌ Actual Behavior

Some requests hang indefinitely during load testing.

Workflow runs remain in “Running” state and are terminated by the system after ~20 minutes.

No clear error or node-level failure information is shown in the UI or logs.

Originally created by @weyuhui110 on GitHub (Oct 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.8.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce <img width="270" height="265" alt="Image" src="https://github.com/user-attachments/assets/7fa9d490-f61c-4258-833b-08a42b0941e1" /> <img width="338" height="605" alt="Image" src="https://github.com/user-attachments/assets/721706a9-0d2a-4e54-be39-a2df9cd8b371" /> <img width="305" height="799" alt="Image" src="https://github.com/user-attachments/assets/4684f884-6202-45aa-8347-d7d23381e786" /> Description When performing load testing on the workflow conversation API, some workflow runs get stuck in the “Running” state. After approximately 20 minutes, these executions are automatically stopped by the system. This issue does not occur under single request conditions — it only appears when concurrency increases (during stress or load tests). When checking the workflow run history, I noticed that: Some parallel branches have partially executed nodes. Subsequent nodes in those branches are never executed. On the UI, all nodes appear as completed, even though some were never actually run. There is no clear indication of which node or branch the execution got stuck on. So effectively, the workflow is partially executed and stuck, but the UI and logs don’t show which node caused the issue. Steps to Reproduce Create a workflow with multiple parallel branches/nodes (around 30 concurrent nodes). Run the workflow through the “workflow conversation API” using a load testing tool (e.g., 100+ concurrent requests). Observe that some workflow runs remain in “Running” state indefinitely. Wait ~20 minutes — the system automatically terminates those stuck runs. Check the workflow run history: you’ll see incomplete execution graphs (some branches not started). ### ✔️ Expected Behavior All workflow executions should complete successfully or fail with a clear error message showing which node or branch caused the problem. ### ❌ Actual Behavior Some requests hang indefinitely during load testing. Workflow runs remain in “Running” state and are terminated by the system after ~20 minutes. No clear error or node-level failure information is shown in the UI or logs.
yindo added the 🐞 bug label 2026-02-21 19:57:20 -05:00
yindo closed this issue 2026-02-21 19:57:20 -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 🐞 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#19234
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?