Assets & tasks / PRACTICAL GUIDE
What to do when an AI generation is pending, slow or failed
Check Generation tasks before submitting the same request again. A slow browser response does not prove that the provider failed. Use the task’s recorded status and result, then decide whether a new request is actually needed.
Understand the state before acting
| State | Meaning to investigate | Next step |
|---|---|---|
| Queued or pending | The request is recorded but not completed | Keep the existing task and check its progress |
| Running | The provider may still be processing | Wait for the task result rather than resubmitting |
| Completed | A result should be available | Inspect and download the result |
| Failed | The request ended unsuccessfully | Read the shown error and check credit records before retrying |
A closed tab or interrupted connection is not itself proof of a failed generation. The server may have recorded a task while the browser stopped receiving updates. The job history is more useful than judging success from a loading animation alone.
Recover the existing task first
- Open Generation tasks in the same account.
- Find the request by product name, time and creation type.
- Use the available refresh or retry-status action to check the recorded job.
- If it completed, open the result and continue with that asset.
- If it failed, review the error and account records before creating a corrected request.
Refreshing an existing job’s status is different from creating another generation. The current video status retry is intended to check the provider task rather than submit a second video. Avoid repeatedly clicking a creation button when the original request already exists.
Correct inputs when the error is actionable
An unsupported aspect ratio, missing reference or invalid duration requires an input change. Insufficient credits requires checking the displayed quote and balance. A provider or network failure may need a later retry, but first establish whether the recorded request completed.
Use the error message shown in the workspace. Do not change API keys or private settings as a routine response to a single slow request. If help is needed, send support the task identifier, time, tool and visible error rather than secrets or unrelated private references.
Keep billing review separate from quality review
A completed result can still fail your product-fidelity review. That is different from a technical task failure. Check purchase and credit records for the actual account state; do not assume that refreshing a page charged again or that a failed-looking animation means credits were refunded.
If a state remains unclear, stop duplicate submissions and contact support with the task details. There is no guaranteed completion time for every provider request. Documenting the existing task gives support a concrete object to investigate and avoids creating more uncertainty through several identical paid jobs.
Sources and further reading
Sources for this page were checked on . Platform rules can change; verify the current source before publishing. Prompt examples and workflow recommendations are Itemlume editorial guidance, not independently measured results.
Frequently asked questions
Does reloading the browser cancel a running generation?
Do not assume so. Check the recorded task in Generation tasks; the provider may still be processing it.
Should I press Generate again when the preview spins?
First inspect the existing task. A new submission can create another request and cost, even when the original is still running.
Does retrying a video status check create a second video?
The current status-retry action checks the existing task. It is separate from confirming a new video generation.
BUILD FROM A PRODUCT YOU KNOW
Put this workflow into practice with your own product.
Explore the relevant tool first. AI copy and concept planning are free after sign-in. Image and video generation require available credits and the applicable account access.
Open Assets & tasks Check pricing and credits