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

A user can invoke up to 6 workflows concurrently and hopes to increase the concurrency #21213

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

Originally created by @yu0407 on GitHub (Dec 22, 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.

I noticed that when one user calls the workflow API, it triggers a maximum of 6 concurrent requests. When two users call the API from two different machines, the server shows a maximum of 12 concurrent requests. I hope there can be a configurable concurrency management feature. I would like to see a single user being able to make 20 or more concurrent requests.

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 @yu0407 on GitHub (Dec 22, 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. I noticed that when one user calls the workflow API, it triggers a maximum of 6 concurrent requests. When two users call the API from two different machines, the server shows a maximum of 12 concurrent requests. I hope there can be a configurable concurrency management feature. I would like to see a single user being able to make 20 or more concurrent requests. ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 20:11:27 -05:00
yindo closed this issue 2026-02-21 20:11:27 -05:00
yindo commented 2026-02-21 20:11:28 -05:00
Author
Owner
Copy Link
Copy Source

@yu0407 commented on GitHub (Dec 22, 2025):

A user can trigger up to 6 concurrent invocations when calling a single workflow API. I hope to increase the number of workflow APIs that a single user can invoke

@yu0407 commented on GitHub (Dec 22, 2025): A user can trigger up to 6 concurrent invocations when calling a single workflow API. I hope to increase the number of workflow APIs that a single user can invoke
yindo commented 2026-02-21 20:11:28 -05:00
Author
Owner
Copy Link
Copy Source

@GaoPatrickStar commented on GitHub (Dec 23, 2025):

I'm running into this concurrency issue as well. I noticed that even when I limit the parallel nodes to 6, one or two of them only start after the others have finished. I'm wondering if this is a configuration issue on my side?

@GaoPatrickStar commented on GitHub (Dec 23, 2025): I'm running into this concurrency issue as well. I noticed that even when I limit the parallel nodes to 6, one or two of them only start after the others have finished. I'm wondering if this is a configuration issue on my side?
yindo commented 2026-02-21 20:11:28 -05:00
Author
Owner
Copy Link
Copy Source

@fatelei commented on GitHub (Dec 26, 2025):

add env NEXT_PUBLIC_BATCH_CONCURRENCY for frontend, you can config it, use latest dify

@fatelei commented on GitHub (Dec 26, 2025): add env NEXT_PUBLIC_BATCH_CONCURRENCY for frontend, you can config it, use latest dify
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 💪 enhancement
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#21213
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?