Troubleshooting

Quick triage

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 checks 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.

Frozen scenes never block your preview from updating. When the check flags one, chat lists the moment to review with a link to it — ask fluos to fix that scene and it reworks just that part.

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 project genuinely takes a while to start.
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

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, free video used. The one-time welcome credits do not renew. Upgrade to a paid plan to keep building; planning and questions still work meanwhile.
• Credits exhausted. Buy a Boost pack or upgrade to a bigger plan for an immediate top-up, or wait for your plan credits to reset next month.

See Plans and Credits.

The agent will not build, it just answers

That is deliberate. fluos decides whether a message commissions video work, and questions get a conversational reply so they do not burn credits on a build. If you wanted a build, be explicit:

Build this now: a 15-second 9:16 teaser using the attached logo.

MCP will not connect

• Confirm the URL is https://www.fluos.io/api/v1/mcp/app for video work, not the public docs server.
• Confirm the host is using Fluos's public OAuth client ID vZg47Po1X1v3rHtU.
• Complete the browser OAuth prompt. A pasted setup prompt cannot skip that step.
• Free plans receive PLAN_REQUIRED. Upgrade from Billing & credits, then retry.
• In Claude Code run claude mcp list and /mcp. In Codex run codex mcp list then codex mcp login fluos. In Cursor check Settings → Tools & MCP.
• If the agent writes config but Fluos never appears, merge the new server instead of replacing existing MCP entries.

Host-specific steps: Claude Code, Codex, Cursor, other agents. Error codes: MCP errors.

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."

Related