Troubleshooting

The problems people actually hit, and what to do about each one.

Quick triage

SymptomLikely causeFirst move
Preview stuck on BootingSandbox still startingWait a minute, then reload the chat
Build failed or timed outComposition too heavy for the time budgetShorten embedded footage or split the request
Video came out silentAudio generation failed during the buildAsk for the narration again
Nothing moves in a sceneMotion was flagged but not repairedAsk fluos to rework that specific scene
Invite will not acceptSigned in with a different emailSign in with the invited address
Upload rejectedWrong type or over the size limitCheck the limits below
Build will not startFree daily build used, or credits exhaustedWait for reset, or upgrade
Export failedRender exceeded its budgetExport 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:

  1. Give it a minute — a cold sandbox genuinely takes a while.
  2. Reload the chat page.
  3. 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

TypeAcceptedLimit
ImagesPNG, JPG, GIF, WebP, SVG10 MB
DocumentsPDF10 MB
SpreadsheetsCSV, XLS, XLSX, XLSM50 MB
VideoMP4, WebM, QuickTime, M4V1 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."