Troubleshooting
The problems people actually hit, and what to do about each one.
Quick triage
| Symptom | Likely cause | First move |
|---|---|---|
| Preview stuck on Booting | Sandbox still starting | Wait a minute, then reload the chat |
| Build failed or timed out | Composition too heavy for the time budget | Shorten embedded footage or split the request |
| Video came out silent | Audio generation failed during the build | Ask for the narration again |
| Nothing moves in a scene | Motion was flagged but not repaired | Ask fluos to rework that specific scene |
| Invite will not accept | Signed in with a different email | Sign in with the invited address |
| Upload rejected | Wrong type or over the size limit | Check the limits below |
| Build will not start | Free daily build used, or credits exhausted | Wait for reset, or upgrade |
| Export failed | Render exceeded its budget | Export at Draft quality, or shorten the video |
The video is not what I asked for
Before assuming something is broken, check the composition stats above the preview. Duration and resolution drifting from the brief is the single most common "it went wrong" case, and it is fixed with one sentence: "make it exactly 20 seconds in 16:9."
If a specific beat is off, name it rather than asking for a redo — "scene 3 holds too long, tighten it to 2 seconds". Broad rewrites tend to lose the parts you liked.
A scene is frozen
fluos measures its own motion and repairs frozen scenes automatically, but a stubborn one occasionally survives. Say which scene and what should move:
Scene 2 freezes after the headline lands. Keep something moving —
a slow push on the background and a subtle drift on the type.For narrated explainers, fluos will refuse to publish a build whose scenes are measurably static rather than shipping a slideshow. If you see that message, retry — it reworks the flagged scenes.
The build failed or ran too long
Builds have a time budget. Common causes of hitting it:
- Long embedded video. Cut a shorter segment: "use only the 0:12–0:18 part."
- Too much in one request. Split it — build the base video, then add narration in a follow-up.
- Very high frame counts. Reduce duration or resolution.
Failed builds are not saved, so nothing you already had is lost. Check Version History if you want to go back a step.
The preview will not start
Order of operations:
- Give it a minute — a cold sandbox genuinely takes a while.
- Reload the chat page.
- Send a small follow-up to trigger a fresh build.
If the preview is unhealthy, exporting is likely to fail too, so fix the preview first.
Uploads
| Type | Accepted | Limit |
|---|---|---|
| Images | PNG, JPG, GIF, WebP, SVG | 10 MB |
| Documents | 10 MB | |
| Spreadsheets | CSV, XLS, XLSX, XLSM | 50 MB |
| Video | MP4, WebM, QuickTime, M4V | 1 GB stored, up to 5 GB accepted and compressed |
If a video sits on Processing or shows Processing failed, press Retry on the card. You can still use it before scene indexing finishes — the agent is just less precise about it.
Invites
Invites are bound to the exact email they were sent to. If acceptance fails, that is almost always why. Other outcomes:
- Already accepted — you are a member; switch workspaces in the sidebar
- Revoked or expired — ask for a new invite
- Sign-in required — you are returned to the invite after signing in
I cannot start a build
Two possibilities:
- Free plan, daily build used. It resets at midnight UTC. Meanwhile, planning and questions still work.
- Credits exhausted. Raise your monthly amount for an immediate top-up, or wait for the next cycle.
See Plans and Credits.
The agent will not build, it just answers
That is deliberate. fluos classifies whether a message commissions video work, and questions get a conversational reply so they do not burn a build. If you wanted a build, be explicit:
Build this now: a 15-second 9:16 teaser using the attached logo.Sign-in problems
Sign out, sign back in, and retry in a clean tab. Confirm you are in the account you expect — having two accounts on different email addresses is a common cause of "my projects are gone."
Still stuck?
Send feedback from the account menu at the bottom of the sidebar. Include the exact error text and what you were doing — it makes diagnosis dramatically faster.