Find a Queued or Missing Generation
Look for the original request in Task list, then check My Works and Usage Records. These views answer different questions: what happened to the task, whether a media result is available, and what was charged. Keep the task ID when investigating a timeout or missing result.
Check the right location
| What you need | Where to look |
|---|---|
| A conversation | Show chat history in the chat workspace |
| An image, video or audio request | Task list in the model workspace |
| Generated media | More actions → Profile → My Works, then the media category |
| A model charge or credit return | Profile → Usage Records |
| A recharge payment | Profile → Payment Records |
Confirm that you are signed in to the account used for the request. Review the selected model and date filters. In Usage Records, choose AI App Platform for workspace usage or API Open Platform for API usage, then search by task ID if available.
If the task is still waiting
Keep its ID and submission time. Check the task’s current message and any relevant site announcements. Queue time depends on the selected service and its current workload; the interface does not provide one fixed completion time for all models.
Before submitting a replacement, determine whether the existing request is still active. If the status remains unclear, use More actions → Contact support with the original task details.
If the browser timed out
Reopen the workspace and inspect the original task. Check My Works for a media result and Usage Records for its associated charge. A browser error alone does not establish the server-side outcome.
My Works warns that files remain on the server for 1–15 days. Save completed files locally as soon as they are available. Avoid clearing task history while you are investigating a missing result.
Next: Troubleshoot a failed task or check usage records.
Last updated