Rivya generation taking too long? Check the original task
Find a waiting image, video or audio task, understand its status, and decide when to wait or retry without accidentally submitting another paid request.
Last reviewed on September 8, 2026
If a generation seems stuck, check the original task before pressing Generate again. A slow page, missing notification or long wait does not by itself confirm failure. A new submission can use credits separately.
Find the original task
Stay signed in to the account that submitted it. Check the original generation page, or open /history/generations and match the model, prompt and creation time. History shows saved task records; reopening it does not guarantee a fresh check with the model service. Notifications can help you find completion or failure updates.
Read the status without guessing a finish time
| Status | What it tells you |
|---|---|
| Waiting | No final result has been recorded yet. |
| Generating | The request is still in progress; this can include an upstream queue. |
| Success | Rivya has recorded a result. Check the output. |
| Failed | Rivya has recorded a failure. Read the error before retrying. |
These states are not a queue position or a remaining-time estimate. The wait alone cannot identify the cause. Task lifecycle explains the stages; there is no single guaranteed completion time for every model and setting.
If the page stops updating
The original generation page checks pending task status periodically. A failed status request or lost connection can interrupt those updates. An unchanged display therefore does not prove the underlying generation has stopped.
Check your connection, then review the saved task and notifications. Closing the tab does not cancel an already submitted task. Reopening a page does not restart or speed it up. If the state remains unclear, contact support with the details below before submitting a duplicate.
Decide whether a new attempt is needed
For a confirmed failure, follow failed tasks and credit returns: read the error, check any returned credits, and correct unsupported settings or incomplete uploads first.
For a successful but unsuitable result, decide which prompt or setting to change. That is a new generation, not a status check or an automatic free retry. Review the new estimate and your balance using credits and billing. Do not send repeated identical requests while the original is still unresolved.
Save a completed result
When the result is available, inspect it and download the output while the file is accessible. An expired link or browser download problem does not mean generation failed. Keep the original result before making another variation.
Get help with an unchanged task
Email [email protected] with your account email, task ID if available, model, creation time and time zone, current status and exact error message. Include when you last checked it. Without an ID, the model and time help locate the record.
Do not send login codes, API keys or confidential source files. Describe sensitive inputs instead. For page or connection issues, also see troubleshooting. Support can investigate the record; this is not a promise of completion or a credit return by a fixed deadline.