dify - 💡(How to fix) Fix param "app_max_active_requests" doesn't restrict active request in streaming mode

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

Community Edition 1.13.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Create a workflow application (preferably one that takes several tens of seconds to process). Set the "app_max_active_requests" param for that application to 2 in the web UI, and publish it. Prepare to call the application API in streaming mode with Dify UI or similar environment, and execute at least three consecutive requests.

✔️ Expected Behavior

Since the "app_max_active_requests" is set to 2, requests starting with the third one will not begin processing until the preceding ones have finished. (Although no detailed definition of this behavior was found in the documentation or other resources, this behavior was observed in version 1.11.0.)

❌ Actual Behavior

Requests starting from the third one onward will also be processed in parallel (up to the limit specified by CELERY_WORKER_AMOUNT etc)