Troubleshooting

Start with the smallest failing action and preserve your project before making changes. The current beta is validated on Windows x64; behavior can vary across builds and environments.

A page or asset is missing

Check the active project, page tab, layer visibility, and selection. Confirm that referenced local files still exist and that you opened the complete project rather than one copied document. If you moved the project, reopen its intended manifest and inspect dependency diagnostics.

For an image, check the selected specification, crop, and placement. For text, check whether its font is installed and whether its bounds allow it to wrap.

An edit is not saved

Finish the current input or Apply action and wait for saving to complete. Read the error near the affected file. Check that the directory is writable and that another application has not changed the source.

Keep unsaved work and recovery files intact. Do not repeatedly restart the editor or delete its profile to clear a save conflict. See Projects and saving.

AI cannot see the project

Confirm the correct running instance and current connection information. Ask the client to inspect the project before writing. A connection to a different editor process can look successful while showing the wrong page. Follow AI connections and keep credentials out of shared reports.

Preview or export looks different

Check the selected document, viewport, fonts, local assets, styles, and output format. An editing view, a page preview, and a generated target can have different support boundaries.

Read the export diagnostic before retrying. A missing target tab may mean that no compatible generator is enabled. If code was generated, build and run that code separately to check the actual result. See Export and generation.

An online feature is unavailable

Production account services, subscriptions, trusted update delivery, and online feedback submission are still in preparation. Do not rely on them as available beta workflows. Where the editor offers offline feedback copying or JSON export, keep that report locally until a verified submission channel is provided.

Prepare a useful report

• Record the editor version from About, Windows version, and the action that failed.
• Describe the expected result, actual result, and smallest steps that reproduce it.
• Include the exact error message and a small sample project if you can share it.
• Remove credentials, personal data, private assets, and unrelated project content from attachments.

Use the support channel supplied with your beta distribution. The company site's Contact entry links to the Cloud Dance organization; it does not imply that every private repository accepts public issue reports.