When WorkBuddy encounters error codes, do not repeatedly submit the same task: 1001 usually points to the model-side state, 3002, 3003, 3007 focus on checking the network, 6003 and 6004 indicate limited request frequency, and 11115 indicates long input content. Grouping the error codes first is usually faster than reinstalling the client.
Which type of problem does the error code correspond to?
| Error code | Common causes | What should we do first? |
|---|---|---|
| 1001、11133、11134、14003 | Current model service exception or session state abnormal | Switch models; 11133 and 11134 can create a new session first |
| 3002、3003、3007 | Network, company agent, or system proxy affect connections | Switch networks and check proxy settings |
| 6003、6004 | When request frequency reaches its limit, the professional version may also encounter it | Pause consecutive submissions or retry the model |
| 11115 | Prompts, attachments, or cumulative context that are too long | Streamlined input, splitting files, or using larger context models |
Network error reports are sorted in this order
- Try retesting on your home network or mobile hotspot to determine if it only appears on the company network.
- WorkBuddy 5.3.0 and later includes a built-in network proxy option; If unclear about the difference, select "Follow System" and confirm that there are no residual expired proxies on Windows or macOS.
- If the company network consistently fails, hand over the error code, occurrence time, and network used to the enterprise IT, focusing on checking proxies, domain access, and security policies.
If the hotspot works but the company network doesn't, it's usually not an account or file issue; If all networks fail, switch models and new sessions to avoid changing multiple variables at once.
Under what circumstances should you not keep retrying?
Frequent clicks on 6003 and 6004 will only create more restricted requests; 11115 cannot be solved by refreshing either. Long tasks should be broken down into three steps: "read data, generate intermediate results, summarize and deliver"; reduce unrelated pages for large attachments first. If the file still reproduces stably after switching networks, models, or new sessions, then submit the client version, system version, error codes, and minimum reproduction steps. Be careful not to include API keys, company files, or bot addresses in screenshots.
