Practical AI Guides

English

简体中文

English

简体中文

Appearance

Troubleshooting Quick Reference: Error Codes and High-Frequency Issues ​

Don't panic when a task fails. Most WorkBuddy errors come with an error code and a one-click action button, and matching your case to the code solves most of them. This page compiles common WorkBuddy error codes, the automatic network reconnection mechanism, and how to handle high-frequency issues like stuck tasks.

Prerequisite reading: Installation: Windows and Mac Main Workflow.

Symptoms ​

You may encounter:

  • A task is interrupted, and an error message and error code appear in the conversation (e.g., 3002, 1001, 4100).
  • A "network connection failure/timeout" prompt appears, and the task is stuck at "Continuously checking network status".
  • The model does not return a usable answer, or the task is stuck and not moving.
  • Credits not received, still showing the Trial edition after upgrading, generated files won't open, unable to read images/PDF/Excel/Word, Bot unresponsive, QR code failure, garbled text and lag.

Quick Checks ​

  • Read the prompt before acting: An error prompt consists of three parts: title, description, and action button. The title states the problem, the description gives the cause and suggestions, and the button is the direct handling entry point.
  • Common buttons: Retry, Switch Model, Check Network, New Task, Log In Again, Configure Model, Submit Feedback, View Documentation. Most errors can be resolved by clicking a button.
  • Confirm your network environment: Are you on a corporate network or a home network? Corporate network issues usually need to go to IT.
  • Check the network proxy: Starting from version 5.3.0, WorkBuddy has a built-in network proxy switch@@I18N_KEEP_000037@@; if you can't tell the difference, use "Follow System".

Troubleshooting Steps ​

Step 1: Match Your Case by Error Code ​

3002／3003／3007: Network connection failure or timeout ​

First confirm whether you are on a corporate network or a home network: for corporate networks, contact your company's IT department; for home networks, follow the official troubleshooting steps one by one, or turn off the network proxy. Tasks that are downloading/uploading can be paused first, or switched to a more stable network.

1001／11133／11134／14003: Model-side exception ​

Switching models and retrying is the first choice; for 11133 and 11134, you can also start a new session and try again.

3008: The model did not return a usable answer ​

Retry later or switch models; if it keeps recurring, submit feedback.

6003／6004: Request frequency limited ​

Switching models and retrying is the first choice. This is a rate limit and can occur even on the Professional edition.

11115: Input content too long ​

Trim down the input content, or switch to a model that supports a larger context.

4100: Custom model not configured ​

Click "Go to Configuration" on the prompt card, complete the model's API endpoint and API Key before using it; it takes effect immediately after saving, no restart needed. For configuration details, see Model Selection and Custom Models.

Step 2: Handle Network Fluctuations and Stuck Tasks ​

When the network fluctuates, WorkBuddy first reconnects automatically, and the task progress area shows "Network issue, attempting to reconnect…". Content already generated and execution records are all preserved.

After automatic reconnection fails, the current conversation pauses output and shows "Continuously checking network status". Once the network recovers, it automatically continues right after the original reply without starting a new round of conversation; if you don't want it to continue automatically, click the close button on the right side of the prompt, and this round is treated as ended. Note: after you manually stop a task, it will not continue automatically.

When a task is stuck and not moving: first use Stop Task to stop the current task, then switch to another model, or simply rerun it.

Step 3: Handle Credits and Account-Related Exceptions ​

  • Credits not received, still showing the Trial edition after upgrading: the official FAQ has corresponding entries; if the prompt says your login status has expired, click "Log In Again"; if that doesn't work, submit feedback with screenshots.
  • A third-party community article documented a system outage in 2026 (month 4): some users' credits were reset to zero and they could not log in; the official side fixed it in about 2 hours and compensated 1000 credits (not an official statement). If you encounter a similar situation, log in again first and watch for official announcements; if that doesn't help, submit feedback.
  • Bot unresponsive, QR code failure, unable to read files, garbled text and lag, etc.: handle these per the corresponding official FAQ entries; if that doesn't work, submit feedback.

When to Escalate ​

For the following situations, stop troubleshooting on your own and escalate directly:

  • 3002／3003／3007 keep recurring on a corporate network: hand it over to your company's IT department.
  • The same error keeps recurring after switching models and retrying (especially 3008 and model-side errors): submit it via "Submit Feedback" with the error code or prompt title attached.
  • Account issues such as credits reset to zero, credits not received, or upgrades not taking effect: submit feedback with order information attached; for refunds, follow the official instructions and file a Tencent Cloud ticket.

One thing to remember when giving feedback: include the error code (if any) or title from the prompt, and it will be handled much faster.

For installation and login errors, see What to Do When Installation Fails: Installation and Login Troubleshooting; for version changes, see Changelog: WorkBuddy Version Timeline.