Help Center› Troubleshooting & FAQ› Sync messages explained

Troubleshooting & FAQ

Sync messages explained

Save status, pending files and cloud delivery describe different steps. Here is what each message can tell you.

More in Troubleshooting & FAQ
  1. Files waiting for the folder
  2. Changes don’t sync
  3. Canvas looks empty
  4. Sync messages explained
  5. Working offline
  6. Privacy
  7. Free vs. paid

What the save status confirms

Status (wording varies by language/version)Meaning
Saved on this deviceThe app has saved locally. Folder delivery may still be pending; this does not confirm that every media original is cached here.
Saved to folderThe app has confirmed its folder save. The cloud provider may still be uploading. This is not an acknowledgement from other devices.

Files waiting for the folder

A calm message appears after a short delay; an unresolved condition becomes an orange warning after about a minute. The colour change is time-based, not evidence of new damage. The count refers to failed element-file operations in a pass; originals or previews can be involved.

See Files could not yet be written to the folder for causes and next steps. A suggestion to keep files available offline is optional guidance, not a diagnosis. You can dismiss it with “Later”.

Access and storage

  • Grant access again: use the app’s folder-access button to restore permission.
  • Folder temporarily unreadable: check the drive, cloud app and local availability. The app waits before replacing shared state it cannot safely read.
  • Saving failed: check storage and access. Automatic retries need the app to be running; a closed browser tab cannot continue them.
  • Local storage unavailable or full: local saving has failed. Keep the session open, resolve storage access and use a complete backup export if possible.
  • Another tab/window: avoid competing sessions for the same workspace.

Sync paused to protect your content

This appears when this device’s state is empty or contains far fewer items than the folder, for example after its local storage was cleared or could not be read. visualOS does not overwrite the folder in that case. If local data could not be read, it keeps retrying and the warning usually clears by itself. If you declined to publish a much smaller state, sync stays paused until the content changes, and you are asked again. Selecting the warning lets you review saved versions; nothing is restored without your confirmation. Do not delete files to remove the warning.

This folder already contains visualOS data

When you connect a folder that already holds a workspace, you choose: load the folder’s data, the usual choice on a second device, or overwrite it with this device’s data. Loading first keeps a copy of this device’s previous state as canvas-data.local-….json in the folder. Overwriting first stores a verified copy of the folder version as canvas-data.replaced-….json; the message afterwards names it. Both copies stay until you delete them. If no copy can be made, nothing is overwritten.

Conflicts and recovery

The app may merge changes, place a conflict copy next to your version, or ask before loading a folder state that contains much less data than this device has seen. See conflicts and Versions.

A warning is useful evidence, but does not by itself establish the cause, data loss, or complete safety. If it persists, share the exact error with support.

Didn’t find what you need?

Tell us what’s missing — feature ideas and bug reports land directly on our roadmap. Or just open the canvas and poke around; you can’t break anything.