The Progress Bar Is Not Moving, or You Closed the Page: What Is Actually Happening

Quick answer: Every generation runs on the server: closing the tab, losing the connection or switching devices does not stop it, and the result is attached to the segment when it arrives. The page only watches: it keeps a live connection for updates and reconnects by itself if it drops; a refresh always shows the true state. The bar is not a countdown. Video is produced by the provider in one piece and reports few intermediate steps, so a bar can sit at the same place for several minutes and then finish. The time shown is the recent average for that tier, from tasks like yours. A job that has really stalled is handled for you after a fixed wait. A video clip moves to checking and the site asks the provider for the result; if it comes, it is attached. A sheet or a text job that times out is marked failed. Whenever the outcome cannot be confirmed, the credits stay held until support reviews them. Nothing needs a click from you.

Still from “Neon Debt”, an AI short drama generated end-to-end by SceneMixer (7 characters, 1 episode) — Sample: “Neon Debt” — Game Engine Realism, 1 episode, produced end-to-end by SceneMixer from the script · watch the episodes

Start a generation, close the tab, come back after a few minutes: the card shows the clip or the current stage.

What the progress bar is showing

Stages, not percent of work: queued (waiting for a free slot), running (sent to the provider), checking (provider took longer than expected; the site is asking it for the result), done or failed. Within running there is little to report — a clip is rendered in one go — so the bar stays still and then jumps. The estimate next to it is the average duration of recent jobs on the same tier. The full list of states: What Each Task Status Means.

The episode timeline: every segment as a card with its thumbnail and duration — The card shows the stage and an estimate; the estimate is an average of recent jobs on that tier, not a countdown.

Closing the page, losing the connection

The server does not know or care whether your page is open. The page keeps a connection for live updates; if the network drops, it reconnects on its own, and if it cannot, the next refresh reloads the real state. Two devices logged into the same account see the same cards. If a card looks frozen for a long time, refresh once before concluding anything.

Queued: why it has not started

Your account runs a limited number of generations at once (3 free, 5 Pro, 8 Studio, 10 Enterprise); the rest wait in your queue and start as slots free up. That is the most common reason a card says queued for minutes. Generating Many Segments at Once.

Slow versus stuck

Slow: running for less than the estimate plus a few minutes; providers vary. Long: a clip’s card moves to checking by itself, and the site asks the provider for the result and attaches it when it comes; a sheet or text job that times out is marked failed. When the outcome cannot be confirmed, the credits are held for review rather than refunded on the spot. You never need to resubmit a running task; doing so would create a second, charged job. What can and cannot be stopped: Stop a Generation.

What to do if it really is wrong

A card that has said running or checking for far longer than any estimate, across a refresh, is worth a report: the Help window’s feedback attaches the project and time. Credits for a task that fails are settled by the rules: When a Generation Fails.

You see	Means	Do
Queued for minutes	Your concurrent slots are full	Wait, or cancel lower-priority queued tasks
Running, bar not moving	Provider rendering in one piece	Wait; refresh once if in doubt
Estimate passed	Recent average exceeded; normal variance	Wait a few more minutes
Checking	Site is asking the provider for the result	Nothing; it resolves by itself
Failed	Settled by the refund rules	Read the message on the card

FAQ

I closed the laptop; is the clip lost?

No. It is attached to the segment when it arrives; open the editor to see it.

The bar has been at the same place for five minutes.

Normal for video; the provider reports little until done.

Can I speed a queued task up?

Cancel other queued tasks, or a higher tier's larger slot count.

Should I submit again if it looks stuck?

No. A second submission is a second charged job. Refresh; then report if it is truly stuck.

Why did the estimate change while waiting?

It is recomputed from recent jobs; busy hours lengthen it.

Let it run

The server finishes the job whether the page is open or not.

Open the editor

Updated September 27, 2026