Follow an image, video or audio request from validation and reserved credits to success or failure. Learn where to find the result and how chat turns differ.

After you submit an image, video or audio request, Rivya records its progress and credit settlement. The task state tells you whether a result or failure has been recorded; it does not measure output quality or tell you exactly when the task will finish.

Before a task can start

Rivya checks the selected model, whether generation is available, the prompt, settings and required reference inputs. Correct a validation error before trying again. A model's documentation page does not mean it is currently callable: check model availability. Audio Isolation is currently unavailable, so its documented upload workflow cannot be started.

Finish required uploads and follow the selected model's file requirements in references and uploads. Rejected inputs do not become a successfully submitted provider task.

Submission and the four states

Rivya creates a waiting task record, then deducts the credits reserved for the request before submitting it to the model service. If there are not enough credits, the task fails without a successful deduction or a provider submission. If the service accepts the request, the task moves into generation.

State	Meaning
Waiting	The task is not finished and has no final result recorded.
Generating	Processing is still in progress; this may include a provider queue.
Success	Rivya has recorded a result. Review the output yourself.
Failed	Rivya has recorded a failure and its error information.

Waiting and generating are not queue positions or remaining-time estimates. Success does not guarantee that the result meets your creative or commercial requirements.

How progress updates reach Rivya

Rivya can receive completion updates from the model service and query its status. If an update arrives before a usable result has been returned, the task can remain pending until the result is available.

The original generation page checks pending status periodically. Connection or query errors can interrupt its display updates. Closing that page does not cancel an already submitted generation. Notifications help you find recorded completion and failure events; a missing notification alone does not prove failure.

What happens to the reserved credits

For a normal confirmed failure after deduction, Rivya returns the reserved credits. If insufficient balance prevented deduction, there are no deducted credits to return for that request.

A successful task can also return part of the reservation when valid final usage is lower. Missing, invalid or above-reservation final usage keeps the reserved amount pending reconciliation; it does not trigger an automatic extra charge. A return marker alone does not tell you whether a task failed or all credits were returned.

Check the amount and time of transactions at /settings/credits, following credits and billing. Returned Rivya credits are not a cash refund to your payment card.

Where to find the recorded result

Use the submitting account and open /history/generations; match the model, prompt and creation time. The current generation history page loads the 24 most recent task records. An older task missing from this view is not proof that it failed or was deleted.

History shows saved records; reopening it does not guarantee a fresh provider status query. Result files can expire even when the successful task record remains. If you cannot find a task, send its ID if available, model, creation time with time zone and account email to [email protected]. Do not send login codes or API keys.

How chat differs

Chat keeps conversations and messages, rather than the same image, video and audio task record. Find them in /history/chats and read saved sessions for returning to a conversation.

A chat turn also reserves credits before calling the model. Valid lower final usage returns the difference; missing, invalid or higher-than-reserved usage leaves the reservation pending reconciliation without an automatic extra charge. A handled failed turn returns its reservation; an insufficient-balance rejection has no successful deduction to return. See Chat Studio for the conversation workflow. Sending another message starts another billable turn, not a generation-status check.

Choose the next step

Still waiting: use generation queues and waiting before submitting a duplicate.
Failed: read failed tasks and credit returns, check the error and transactions, then correct the cause before another attempt.
Successful: inspect and download the result while available. A new variation is a new request with its own credit estimate.

Rivya task states: submission, results and credits