Understand Rivya generation queues, waiting times, long-running image, video, and audio tasks, notifications, history, and safe retries.

Use this guide when a Rivya image, video, or audio task stays in progress longer than expected.

Video, audio, reference-heavy image work, provider queues, and larger generation settings can all make a task slower than a normal page interaction. Waiting does not by itself mean failure.

What A Queue Means

A queue means the task has not finished yet.

That may happen because:

the provider is processing the request
the workflow takes longer by design
the input includes files or references
the output setting is heavier
temporary demand is high
Rivya is waiting for a callback or status update

A queued task should be tracked through task status, notifications, and history rather than repeated immediately.

Waiting Is Not The Same As Failure

A task can be:

submitted
processing
waiting for provider result
completed
failed

Do not treat every long-running task as failed. Check the status before retrying.

For failure behavior, read Failed Tasks and Credit Refunds.

Where To Check Progress

Use these places:

the workflow page where the task started
Rivya Notifications Center
History in Rivya
account credit and task state where available

Notifications help because async generation should not depend on a single toast that disappears.

What To Do While Waiting

While a task is processing, you can:

prepare the next prompt variation
review previous history
plan how the output will be used
avoid submitting duplicate tasks too quickly
switch to another task if the current one is asynchronous

If the task is important, wait for a final status before assuming the result is lost.

When To Retry

Retry when the task clearly failed, the input was wrong, or the output is not useful.

Before retrying, decide what changed:

simpler prompt
fewer references
different model
different duration or quality
corrected upload
clearer task intent

Repeating the same request without changing anything may repeat the same problem.

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 most useful result before branching into another workflow.

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

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.

Generation Queue and Waiting Times