Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors are reported during batch processing, and timeouts often occur when calling the application API. Is there an access threshold setting on the platform? #15155

Closed
5 tasks done
ricky977 opened this issue Mar 7, 2025 · 1 comment
Labels
🐞 bug Something isn't working outdated version smaller than 0.13.2

Comments

@ricky977
Copy link

ricky977 commented Mar 7, 2025

Self Checks

  • 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 (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue,否则会被关闭。谢谢!:)
  • Please do not modify this template :) and fill in all the required fields.

Dify version

10.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Image
Moreover, when calling the application apide through multiple threads concurrently, timeouts will occur at intervals. Is there a threshold limit for concurrent execution or concurrent API calls on the platform? Where can I control it?

✔️ Expected Behavior

Stable operation step by step

❌ Actual Behavior

After running for a while, an error is reported,keep prompting to retry.Moreover, when calling the application apide through multiple threads concurrently, timeouts will occur at intervals. Is there a threshold limit for concurrent execution or concurrent API calls on the platform? Where can I control it?

Copy link

dosubot bot commented Mar 7, 2025

There is a threshold limit for concurrent execution on the Dify platform. You can control this limit using the APP_MAX_ACTIVE_REQUESTS parameter in the AppExecutionConfig class. By default, it is set to 0, which means unlimited concurrent requests. You can set a specific non-negative integer value to limit the number of concurrent active requests per app [1].

Additionally, there are known issues related to concurrent API calls in Dify version 10.2. Specifically, when multiple users access the Dify API service simultaneously, there can be long wait times for responses. This issue is caused by the Opik SDK attempting to fetch a configuration file from GitHub upon service restart, even for users who do not use the Opik feature. The maintainers plan to optimize this by delaying the import timing of the Opik SDK for users who don't use it [2].

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

@dosubot dosubot bot added the 🐞 bug Something isn't working label Mar 7, 2025
@crazywoola crazywoola added the outdated version smaller than 0.13.2 label Mar 7, 2025
@crazywoola crazywoola closed this as not planned Won't fix, can't repro, duplicate, stale Mar 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working outdated version smaller than 0.13.2
Projects
None yet
Development

No branches or pull requests

2 participants