A task keeps waiting, fails, or finishes only partially
TroubleshootingReview draft
On this page
Return to the original conversation and check the latest status and unanswered questions. No new output can mean the task is reading materials, executing a step, or waiting for you.
Still waiting
Check the latest execution step, requests for information, and manual generation confirmation. Answer or confirm when required. If execution continues, follow its progress instead of submitting the same request again.
After a network interruption, reopen the original conversation. A disconnected page does not mean the background task stopped.
An explicit failure
| Error | Next step |
|---|---|
| Connection error, timeout, or generation failure | Check connectivity and task status, use the provided retry action, and record persistent errors. |
| Unavailable reference | Check that the source exists, is accessible, and has finished processing; reference it again. |
| Insufficient credits | Check the current workspace balance and your member allowance. |
| Member allowance exhausted | Ask an authorized administrator to review your allowance. |
| Storage limit | Resolve workspace capacity before retrying. |
| Content not allowed | Review the materials and request; report questions instead of repeatedly submitting identical content. |
Partial success
Keep useful successful outputs and identify exactly what failed. Specify the missing part when requesting more work; do not assume retry executes only missing items. Reference completed outputs to preserve direction.
An output that misses the goal needs revised instructions or materials. A task with no output and an error needs troubleshooting. Do not treat both as a reason to repeatedly regenerate.
For recurring failures, record the time, project, conversation, error, input materials, and retry history.
Progress, stop, and retry · Credit issues · Contact support · Documentation