↓
Rivya AI Docs

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 November 6, 2026

If an image, video or audio task fails or seems stuck, find the original task before submitting again. A new generation can reserve credits even if you reuse the same prompt.

Check the original task

Open /history/generations in the account that started the task. Use the model, creation time and any prompt you supplied to identify it, then read the 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 recorded state.

Task stateWhat to do
WaitingThe task has not finished. Check the existing task before submitting a duplicate.
GeneratingRivya is waiting for a result or confirmation of the request. A slow response is not a confirmed failure.
SuccessA result was recorded. Check the output separately for download access and quality.
FailedRead the error and check the credit transactions before deciding whether to retry.

The Task lifecycle explains task states and credit settlement. Closing the page stops its status display from updating; it does not cancel an already submitted generation. A lost browser connection does not, by itself, confirm failure.

Check returned credits, not just the badge

Rivya deducts the reservation before sending a billable generation to the model service. When it handles a confirmed rejection or failure after that deduction, it returns the reservation. 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 return part of its reservation when valid final usage is lower. The credit-return badge in History can therefore mark a partial return on a successful task. It does not, by itself, mean the task failed or that all credits were returned. Check the transaction amount.

Missing final usage normally leaves the reserved amount pending reconciliation. Eligible fixed-price Runway and Suno Sounds generation requests can settle at the reservation when it matches their recorded quote. Invalid or above-reservation usage stays pending; Rivya does not automatically deduct more credits.

Disliking the output does not change a successful task to Failed or trigger an automatic credit return. Contact support if the task record and credit transactions do not agree.

If the task is still processing

Reopen the original task in History and check notifications before submitting again. History reads the saved record; opening it does not itself force a new model-service status check. A page error or a long wait does not confirm that the generation stopped. See Queues and waiting.

An interrupted or contradictory response may leave submission unconfirmed. Reserved credits stay held for reconciliation, including when no provider task ID was returned. Check the original task or conversation and credit history before submitting again. A page refresh does not cancel a request or confirm a refund.

For a paid extension or resolution upgrade, check the action's own task and credit transactions. Its reservation is separate from the original generation, and the original video's Success state does not confirm the upgrade's result.

If the status stays unchanged and you need help, send support the details listed below. Completion and credit returns have no guaranteed turnaround time.

Fix one cause before trying again

  1. Read the error message. If it identifies an unsupported field or missing input, correct that item first.

  2. 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 you make the instructions clearer, but keep every required input. It does not guarantee success.

  3. Check Model availability and the model's supported settings. A paused model cannot be made available by repeatedly submitting the same request.

  4. Review the new credit estimate and your balance, then submit one corrected request. It may reserve credits again. Use the existing task's status check to look for an update; starting another generation or a paid result action is a separate request.

If the same error repeats, keep any task records and contact support instead of sending more identical requests.

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.

If a chat reply is interrupted

If a chat reply stops partway through, look for the saved conversation at /history/chats before sending another message. The Retry button for a session-loading error tries to reload saved messages; it does not resend your message. Sending the same message again creates a new turn and may reserve credits.

Rivya returns a reservation when it handles a failed turn before saving the reply. If the turn was rejected for insufficient credits, there was no successful deduction to return. A connection error can occur after a reply has been saved, so check the conversation and credit transactions before assuming the turn failed. Chat Studio explains the conversation workflow.

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 look into the recorded task and credit transactions; a cash refund or a successful replacement generation is not guaranteed.