[GH-ISSUE #387] Server Capacity Issues - "The server is busy" Errors #306

New issue

Closed

opened 2026-10-26 21:19:07 +00:00 by bsakaguchi · 3 comments

bsakaguchi commented

2026-10-26 21:19:07 +00:00

Owner

Originally created by @Jeanga7 on GitHub (Feb 12, 2025).
Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-R1/issues/387

Description

Users are receiving "The server is busy. Please try again later." errors when attempting to use the service. This error appears to be blocking access to core functionality.

Steps to Reproduce
Attempt to access DeepSeek services
Receive immediate error message: "The server is busy. Please try again later."

Expected Behavior
Server should process requests within reasonable time
If at capacity, implement a queue system or provide more specific wait times
Proper load balancing to handle user requests

Current Behavior
Immediate rejection of requests
Generic "server busy" message
No indication of when service might be available again

Impact
Users cannot access the service
Disrupts workflow and productivity
No clear timeline for resolution

Suggested Solutions
Implement proper queue system for requests
Add more server capacity
Show estimated wait times to users
Consider implementing a priority system for critical requests

System Information
Time of occurrence: [2:00 PM]
Browser/Client: [chrome]
Location: [Sénegal, Dakar]

Originally created by @Jeanga7 on GitHub (Feb 12, 2025). Original GitHub issue: https://github.com/deepseek-ai/DeepSeek-R1/issues/387 ### **Description** Users are receiving "The server is busy. Please try again later." errors when attempting to use the service. This error appears to be blocking access to core functionality. **Steps to Reproduce** Attempt to access DeepSeek services Receive immediate error message: "The server is busy. Please try again later." **Expected Behavior** Server should process requests within reasonable time If at capacity, implement a queue system or provide more specific wait times Proper load balancing to handle user requests **Current Behavior** Immediate rejection of requests Generic "server busy" message No indication of when service might be available again **Impact** Users cannot access the service Disrupts workflow and productivity No clear timeline for resolution **Suggested Solutions** Implement proper queue system for requests Add more server capacity Show estimated wait times to users Consider implementing a priority system for critical requests **System Information** Time of occurrence: [2:00 PM] Browser/Client: [chrome] Location: [Sénegal, Dakar]

bsakaguchi

2026-10-26 21:19:07 +00:00

closed this issue
added the
stale

closed-as-stale
labels

bsakaguchi commented

2026-10-26 21:19:08 +00:00

Author

Owner

@CSYuq1 commented on GitHub (Feb 13, 2025):

大家现在都是这样，用的人太多了

@CSYuq1 commented on GitHub (Feb 13, 2025): 大家现在都是这样，用的人太多了

bsakaguchi commented

2026-10-26 21:19:08 +00:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 23, 2025):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this issue is still relevant, please leave a comment to keep it open. Thank you for your contributions!

@github-actions[bot] commented on GitHub (Mar 23, 2025): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you believe this issue is still relevant, please leave a comment to keep it open. Thank you for your contributions!

bsakaguchi commented

2026-10-26 21:19:08 +00:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 27, 2025):

false

@github-actions[bot] commented on GitHub (Apr 27, 2025): false

bsakaguchi referenced this issue

2026-10-26 21:26:40 +00:00

[PR #306] Update README.md to correct grammatical tense #778