↓
Rivya AI Docs

Rivya Browser, Upload, and Playback Requirements

Troubleshoot browser, upload, connection, and playback issues in Rivya. Save unsent work before refreshing and check existing tasks before submitting again.

Last reviewed on November 5, 2026

Identify the step that failed: opening the page, uploading a file, submitting a task, or opening a finished result. If the error appeared after submission, check for an existing task before sending the request again.

Set Up the Browser for the Task

Use an up-to-date browser with the site's scripts and sign-in session enabled. Keep a stable connection while uploading and submitting. If Rivya behaves unexpectedly in a browser embedded inside another app, open it directly in your regular browser and check the same page again.

SymptomFirst check
Page or form does not loadConfirm the address and network connection, then check whether an extension is blocking this site
Upload or submit asks you to sign inCheck the active account; see sign-in and access
A copy button does not copy textSelect and copy the visible text manually; verify the pasted text before leaving the page
A result opens in another tab instead of savingUse the browser's save or download control on that result; see output downloads

If an extension appears to interfere, temporarily test without that extension for this site and restore your preference afterward. Do not start by clearing all browser data: it can sign you out and does not resolve an unsupported model input.

Protect Your Work Before Refreshing

  1. Copy unsent prompts or chat text to a local note. If a copy button fails, use manual selection and confirm the text was actually saved.

  2. Record the model, operation, settings, and any visible task identifier. Keep the original reference files on your device.

  3. If you already submitted, check History or the correct saved conversation before refreshing or sending again. Your unsent text may still need to be saved separately.

  4. After saving this information, refresh or reopen the page. Check the active account, model, settings, and displayed references before continuing. Re-upload prepared files only where the selected operation supports them. Follow login and draft protection when signing in changes the page.

A different browser or device does not automatically receive your unsent text, selected local files, or every setting. A saved task or conversation must belong to the account you use to open it.

Check the File Against the Selected Operation

Check model availability and reference-file requirements before changing browsers. Type, size, count, dimensions, aspect ratio, duration, and supported combinations depend on the model and mode. A file that opens on your device can still be invalid for that operation.

Open the original locally to check that it is readable. If conversion is needed, export a separate copy in an accepted format; changing the filename extension does not convert the file. Keep any required minimum dimensions when reducing its size. Prepare the copy with the safe-upload guide, then confirm that the uploaded reference appears in the form before submitting.

A JPEG, PNG, or WebP file that previews locally still needs a supported image input on the selected model. The currently available chat models take text only; they do not offer image, PDF, spreadsheet, audio, or video attachments. For recording-based work, read audio uploads to check whether the selected operation accepts a recording.

Separate Connection Errors from Task Status

The generation form periodically checks an existing running task. If those checks fail, the form can show that status is temporarily unavailable. An unchanged page does not tell you whether the task stopped. Losing the response to a submission can also leave you unsure whether the request was accepted.

Restore the connection and check the existing task. Use queue and waiting guidance for an in-progress task and failed tasks and credit returns for a recorded failure. Do not infer failure, cancellation, a refund, or a completion time from a browser message alone. A second submission can create another task with its own credit cost.

Before retrying an upload, check which references are already displayed in the form. Before submitting a generation again, check the earlier request and resolve the reported issue. Change one relevant input at a time so you can tell which change helped.

Open and Save Finished Results

Open the available result link and save a local copy if you need the file. For image, video, and audio media in History, the download action opens the primary output in a new tab; your browser may display it before you save it. Text results have their own download control. Check the saved file as well as the preview.

For video or audio that will not play, try the downloaded file in a compatible player if the link still works. Playback support depends on the media format and encoding, so an MP4 extension alone is not a complete compatibility check. The MDN media-format guide explains that distinction.

A preview error means the browser could not display that result. Check the saved task and the existing file link before paying for a replacement. If the link is expired or unavailable, follow the download guide for retention and expired-output handling. Review image dimensions, sound, duration, and editing needs before using the result.

Send Useful Details When You Need Help

If the problem persists, follow troubleshooting or use Contact. Include the page or model, browser and version, device, approximate time, exact visible error, and task identifier if available. For file issues, add format, size, relevant dimensions or duration, and the point where the process failed.

A cropped screenshot without private details can help. Do not share passwords, API keys, verification codes, raw session data, or private media access links. State whether the task appears in History and what you already tried so the next check can target the actual failure.