Rivya task states: submission, results and credits
Understand Rivya's image, video and audio task states, reserved credits, saved results and chat turns. Know what to check before sending another request.
Last reviewed on November 5, 2026
Once Rivya creates a task for an image, video or audio request, you can follow its state and credit settlement. The state says whether a result or failure has been recorded; it does not rate the output or estimate when it 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. If Rivya rejects the inputs during validation, the generation is not sent to the model service.
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. A task record alone is not proof of a deduction or provider acceptance. If the balance is insufficient, the task fails without a successful deduction or provider submission. A confirmed submission moves the task to Generating.
If a Veo generation or extension submission has an unclear response, Rivya keeps the task and reservation pending. Generating can therefore include a request whose acceptance is unconfirmed, as well as processing or a provider queue. Check the existing task before submitting another request.
| State | Meaning |
|---|---|
| Waiting | The task is not finished and has no final result recorded. |
| Generating | Rivya is waiting for the model service's result or confirmation of the request. 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 do not show your queue position or a completion-time estimate. Success means a result was recorded; it does not guarantee that the output fits your creative or commercial needs.
How progress updates reach Rivya
Rivya receives model-service updates and checks the recorded request where supported. An update without the result data needed to finish the task can leave it pending. For a separate Veo 4K upgrade, the original video's Success state does not confirm that the upgrade is finished; use the upgrade's task record.
The generation page periodically checks pending tasks. A connection or status-query error can pause those display updates. Closing the 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
When Rivya handles a confirmed model-service rejection or generation failure after a successful deduction, it returns the reservation. If insufficient balance prevented deduction, no credits were taken for that request. Check the credit transaction before assuming a return is complete.
A successful task can return some credits when valid final usage is lower than the reservation. Missing final usage normally leaves the reservation pending reconciliation. Eligible fixed-price Runway and Suno Sounds base generation requests can settle at the reservation when it matches their recorded quote; this does not cover add-on actions or Chat. Invalid or higher-than-reserved usage remains pending, without an automatic extra deduction. A credit-return notice can mean a partial return on a successful task. It does not, by itself, mean the task failed or that the full reservation was returned.
Review the amounts and times of transactions at /settings/credits; see credits and billing for the rules. Returned Rivya credits are not a cash refund to your payment card.
Where to find the recorded result
Use the account that submitted the request and open /history/generations. Match the model and creation time, and the prompt if one was provided. The generation history page lists the newest tasks first, with up to 24 records per page. Use search and pagination to find older tasks; not seeing one on the first page does not mean it failed or was deleted.
Reopening History reads the saved task record; it does not itself force a new model-service status check. Result files can expire even while the 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 uses conversations and message turns, rather than the image, video and audio task workflow. Find saved conversations in /history/chats and read saved sessions for returning to one.
A chat turn 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.
When Rivya handles a failed turn whose reply has not been saved, it returns that turn's reservation. An insufficient-balance rejection has no successful deduction to return. A browser error or an interrupted reply does not, by itself, confirm failure or a credit return. See Chat Studio for the conversation workflow. Sending another message, including resending the same one, starts a new turn and may reserve credits again; it is 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, and address any input or account issue before another attempt.
Successful: inspect and download the result while available. A new variation is a new request with its own credit estimate.
