Troubleshoot common workflow problems

Diagnose sync, missing entities, AI targeting, generation, import, export, and permission issues from the correct layer.

A scene or location is missing

Return to the screenplay and inspect the scene heading. Scenes and locations are derived from semantic heading nodes. Reformat pasted plain text as a scene heading and normalize the location name. Do not try to create a disconnected scene database row.

AI edited the wrong place

Stop and use history if the change is broad. Then select the exact text or place the cursor in the target scene, name the episode, list what must stay unchanged, and request a bounded correction. Cross-episode work must switch to a real episode rather than infer one.

AI cannot write

Check your project role. Viewer and unresolved roles are read-only. A creative craft identity does not grant write access. Worldview also requires an explicit write request in the latest message even when you can edit the project.

Changes appear local or collaborators are absent

Read the connection and presence indicators. Allow the local document to reconnect instead of opening duplicate tabs. Remember that collaborators can be online in different episodes and dimensions without sharing your current view.

FDX import fails

Confirm the file is an FDX Script document, not another Final Draft document type. Review file size and unusual embedded content. Cinema projects do not support FDX. Import creates a new project rather than merging into an existing one.

Export format is unavailable

Hollywood script supports PDF, DOCX, TXT, and FDX. Asian script supports PDF, DOCX, and TXT. Outline supports PDF, DOCX, and TXT. There is no Fountain export. Also check membership and whether the owner allows Viewer export.

A generation seems stuck

Check the task card rather than dispatching duplicates. Queued and running tasks keep their own status and estimate; refresh or navigation should reconcile them. For failure, read the terminal message, confirm credits and references, then retry only after correcting the cause.

When to contact support

Preserve the project URL, task or version timestamp, browser and app version, visible error, and the smallest reproducible steps. Do not send passwords, private API credentials, or unrelated source files.