Rivya failed tasks: check status, credits and retries
Find a failed or pending generation, check returned credits, and decide what to fix before retrying. Separate generation errors from download and quality issues.
Last reviewed on September 8, 2026
If an image, video or audio task fails or seems stuck, find the original task before submitting again. A new generation request can spend credits even when it repeats an earlier prompt.
Check the original task
Open /history/generations in the account that started the task. Match the model, prompt and creation time, then read its status and error message. See History for finding previous work. The Notifications Center can help you find completion or failure updates; use the task record to check the current state.
| Task state | What to do |
|---|---|
| Waiting | The task has not finished. Check the existing task before submitting a duplicate. |
| Generating | Work is in progress. A slow response is not a confirmed failure. |
| Success | A result was recorded. Check the output separately for download access and quality. |
| Failed | Read the error and check the credit transactions before deciding whether to retry. |
The Task lifecycle explains how a submission reaches a final state. Closing a page or losing a browser connection does not by itself establish that the task failed.
Check returned credits, not just the badge
Rivya reserves credits by deducting them before sending a billable generation request for processing. In the normal failure flow, a confirmed generation failure after that deduction returns the reserved credits to your account. A request rejected for insufficient credits has no successful deduction to return.
Open /settings/credits and inspect the amount, time and description of usage and credit-return transactions. A credit return goes to your Rivya balance, not your payment card. See Credits and billing for spending and settlement rules.
A successful task can also return part of its reservation when valid final usage is lower. The history refund badge can therefore indicate a partial return on a successful task; it does not by itself mean a full refund or a failed generation. Check the transaction amount. If final usage is missing, invalid or above the reservation, Rivya keeps the reserved charge pending reconciliation rather than automatically deducting more.
A result you dislike is not automatically a failed task. The automatic failure refund is not a satisfaction guarantee. Contact support if the task record and credit transactions do not agree.
If the task is still processing
Reopen the original task through history and check notifications before submitting again. Do not assume that a page error or a long wait has stopped the underlying generation. See Queues and waiting.
If the status remains unchanged and you need help, send support the task details below. This guide does not promise a fixed completion or credit-return time for every model.
Fix one cause before trying again
Read the error message. If it identifies an unsupported field or missing input, correct that item first.
Check that uploads completed and meet the selected model's type, size and reference limits. See References and uploads. A simpler reference set may help clarify conflicting instructions; it does not guarantee success.
Check Model availability and the model's supported settings. A paused model cannot be made available by repeatedly submitting the same request.
Review the new credit estimate and your balance, then submit one new attempt with the correction. Each new submission is a separate billable request; checking an existing task's status is not a new generation.
If the same error repeats, keep both task records and contact support instead of continuing a series of identical paid attempts.
If a successful result will not download or needs editing
Check whether history shows that the result has expired. An expired output link or a browser download problem is separate from a generation marked failed. Follow Output downloads and save useful files while they are available.
If the file opens but the composition, wording, pronunciation or motion is wrong, review the prompt and settings before another generation. Keep the original result for comparison. For page or browser issues, use Troubleshooting.
Details to send support
Email [email protected] with the account email, task ID if available, model, creation time with time zone, displayed status and error text, and relevant credit transaction amounts and times. Include the settings and file type/size that may explain the issue. If you cannot find a task ID, the model and time can help locate the record.
Do not send login codes, API keys, full card details or confidential source files. Describe sensitive inputs without attaching them. Support can investigate the recorded task and billing; this guide does not promise a cash refund or a successful replacement generation.