Use Rivya saved sessions to continue chats, prompt drafts, tool conversations, generation context, project decisions, and longer workflows.

Use this saved sessions guide when a chat, prompt draft, planning thread, tool conversation, or generation context needs to stay useful across more than one visit.

Saved sessions keep work from becoming disposable.

They help you return to planning, prompts, decisions, and useful context instead of restarting every project from memory.

What Saved Sessions Are For

Saved sessions are useful for:

multi-turn chat planning
prompt drafts
campaign notes
product direction decisions
image or video brief preparation
follow-up work after generation
remembering why a direction was chosen

They are especially useful when a project takes more than one sitting.

What To Save

Save context that would be annoying to reconstruct:

the original goal
audience notes
product facts
model or workflow decisions
prompt versions
review comments
next-step reminders

A saved session should help you continue work, not just store old messages.

Sessions, History, Notifications

Use saved sessions for reasoning and planning context.

Use History for generated outputs, task results, and files you may need to reopen. Use Notifications for async status changes, failures, low-balance events, and billing-related updates.

When a project moves from Chat into Image, Video, Audio, or Tools, keep the saved session as the planning thread and History as the output record.

When To Use Both

Chat sessions and generation history are related but not identical.

Saved chat helps preserve reasoning and planning.

Generation history helps preserve outputs and task results.

Use both when a project moves from planning into production.

Review Before Continuing

Before continuing a saved session, review:

what the last decision was
which prompt version was strongest
what still needs to be generated
whether any assumptions have changed
which Studio or workflow should be used next

This avoids continuing from outdated context.

Task Continuity Checklist

When a task needs to stay traceable after submission, check:

Check whether the task is pending, running, completed, failed, or ready for follow-up.
Use History for useful outputs and Notifications for async status changes.
Keep the task UUID, model, prompt, and output context together when troubleshooting.
Do not restart the same job until the current state is clear.
Save or download the strongest result before branching into another workflow.

The goal is to avoid losing work when a generation takes time or needs follow-up.

Common Continuity Mistakes

Avoid treating saved sessions as the only project record.

Common mistakes include saving a chat but not the generated output, restarting a task before checking status, losing the prompt version that produced the useful result, or moving into another Studio without carrying the decision context.

If the next step depends on an output, check History first. If it depends on the reasoning behind the output, reopen the saved session.

When To Recheck Status

Recheck status when a task takes longer than expected, a notification is missing, a result appears incomplete, or a user cannot find a previous output.

In those cases, inspect the task state and History before asking the user to regenerate.

Rivya Saved Sessions Guide