Handle Rivya failed tasks, credit checks, retries, upload issues, provider errors, notifications, history, and processing states.

Use this guide when an image, video, or audio generation fails, appears stuck, or finishes without a usable result.

It explains where to check task status, how credit handling works, and what to change before spending credits on another run.

What Counts As A Failed Task

A failed task is different from a task that is still processing.

A task may be failed when Rivya or the provider reports that the generation cannot complete. A task may still be processing when it has been accepted but the result has not returned yet.

Before assuming a task failed, check the task status in the relevant history or notification surface.

How Credit Refunds Work

Rivya's task lifecycle is designed to reserve credits for generation work and handle failed outcomes according to the product's current billing logic.

In practice, check the task result, task status, and credit balance after a failed generation. If the task failed before producing a usable result, Rivya may return credits according to the current failure-handling path.

Because provider behavior can differ by workflow, do not assume that every delay is a failure or that every retry should be submitted immediately.

Where To Check Task Status

Use these places first:

the generation history for the workflow
Rivya Notifications Center
account credit balance
the page where the task was started

For the underlying flow, read Task Lifecycle in Rivya.

What To Try Before Submitting Again

Before retrying, check:

whether the upload finished correctly
whether the file type and size are supported
whether the prompt asks for unsupported behavior
whether the selected model is currently appropriate for the job
whether the task is actually still processing
whether a simpler first run would be safer

If the task uses references, try reducing reference complexity or clarifying what each reference should control.

When A Task Is Still Processing

Some generation tasks take longer than a normal web interaction.

If the task is still processing:

avoid submitting repeated duplicates immediately
check notifications for updates
return through history when available
wait for the final status before treating it as failed

Asynchronous work is one reason Rivya keeps notifications and history separate from one-time page toasts.

Retry Checklist

Before retrying a failed or unclear generation, check:

Confirm the exact task status before starting another run.
Check the upload, prompt, model, and settings that were used.
Decide what should change in the retry: simpler prompt, fewer references, different model, or corrected file.
Check credit balance and expected cost before using a heavier setting.
Keep the failed task context available if you need to troubleshoot or contact support.

The goal is to retry with a clearer reason, not to repeat the same failed request.

When To Recheck Before Retrying

Recheck before retrying when the task is still processing, the credit state is unclear, or the same upload or prompt has failed more than once.

In those cases, inspect history, notifications, and task state before starting a duplicate run.

Rivya Failed Tasks and Credit Refunds Guide