↓
Rivya AI Docs

Rivya History Guide

Find recent generations and saved chats in Rivya, download available results, reuse images, and understand history and file-expiry limits.

Last reviewed on September 8, 2026

Sign in to the account that created the work, then open generation history for images, videos, and audio, or chat history for saved conversations. Download useful files while they are available; a task record is not a permanent file backup.

Find the Right Record

Open /history/generations and match the model, creation time, and prompt preview. The current page loads the most recent 24 tasks and has no control for loading older pages. An older task missing from this list does not establish that it failed or was deleted.

Open /history/chats for conversations, including chats started through tools. The 24-task limit applies to generation history, not this chat list. Use the title, model, tool badge when present, date, and last-message preview to identify a session.

Read a Generation Card

A card shows the model, media type, creation date, prompt preview, saved task status, and a credit figure. When available, it also shows a result preview, error message, credit-return marker, or media-expiry notice.

The credit figure is the task's recorded estimate, not necessarily its final net charge. A return marker can mean a partial credit adjustment after a successful task. Check /settings/credits for the transactions and amounts; see Credits and Billing.

Waiting or generating is not a completion deadline. History displays saved status and does not guarantee a fresh provider check whenever you open it. For status changes and settlement, see Task Lifecycle.

Download Before Files Expire

For an available result, choose the download action. It opens the result URL in a new tab; depending on your browser and the file, you may need to use the browser's save or download control.

A card can remain after its media expires. When Rivya marks media as expired, the preview and download action are no longer available on that card. A remaining-days notice is a reminder to save the file, not a guarantee that the remote link will always load until then. Keep your own copy of useful work.

A broken link or expired file does not by itself mean the generation failed or qualifies for a credit return. See Output Downloads for saving and checking results.

Reuse a Result

“Open workspace” opens the model's workspace and carries over the prompt. For a supported image model, it can also carry an available image result as a reference. It does not restore every setting or reopen the original task as an editable project.

Available image results may offer actions to animate the image or discuss it in chat. Other eligible results can show model-specific actions such as extension, higher-resolution output, WAV conversion, or vocal separation. These actions depend on the model, original task, and available source media; they are not offered for every result.

Before submitting a follow-up, check the destination model, inputs, settings, and credit estimate. Opening a workspace is not the same as submitting a new request. Use Image Workflows, Video Workflows, or Audio Workflows for the next step.

Continue a Saved Chat

Choose the continue action on the matching chat card. It opens that session at /studio/chat/session/[sessionId], with its saved conversation, rather than a blank chat.

Review the conversation before sending another message. A new message starts another billable turn under that model's credit rules; opening the saved session is not a new generation request. See Chat Workflows and Saved Sessions.

If Work Seems to Be Missing

Check the account and history type first, then the generation list's 24-task limit. For a known task, compare the original generation page and Notifications Center. A missing notification alone does not prove failure. The Dashboard provides a recent overview, not a complete archive.

If you still cannot locate the work, contact [email protected] with your account email, model, approximate creation time and time zone, and task or session ID if available. Describe any error without sharing login codes or API keys. Do not submit the same generation again just to find its status: a new submission can incur another charge.