DeepSeek Load Balancing Bug

[walden668]

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

0.12.1

Cloud or Self Hosted

Cloud

Steps to reproduce

Reporting a bug: DeepSeek load balancer triggers an error approximately every two attempts.
I've verified that all keys are working fine - direct API calls to the official endpoint using curl work normally.

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

[dosubot]

@walden668 Hello there! I'm here to help you with bug reports, answer your questions, and assist you in becoming a contributor. Let's tackle this issue together while we wait for a human maintainer.

The issue you're experiencing with the DeepSeek load balancer might be related to its request distribution mechanism. The load balancer uses a Round-robin strategy, which can lead to intermittent failures if rate limits are triggered. When these limits are exceeded, a 1-minute cooldown period is applied, potentially causing temporary unavailability and resulting in errors approximately every two attempts ^[1].

To address this, you might want to check if the rate limits are being exceeded and adjust your request patterns accordingly. If the issue persists, further investigation into the specific error messages or logs generated by the load balancer could provide more insights.

To continue talking to Dosu, mention @dosu.

[walden668]

I've confirmed that no rate limit was triggered, since the returned error is a 401 auth error

[crazywoola]

Can you paste the text errors as well?