Troubleshoot read-only, save, update, and feature limits

When an action is unavailable, first decide whether the cause is permission, storage, connectivity, an update, or a current Editor v2 limit. Protect the open work before reloading, replacing a document, or changing accounts.

The representative video demonstrates this exact workflow: Open the Editor v2 file menu and verify that New file and Duplicate remain unavailable instead of presenting either action as successful.

Verified result: The file menu is open and both New file and Duplicate are visibly disabled. The document is unchanged.

Recognize current file limitsOpen the Editor v2 file menu and verify that New file and Duplicate remain unavailable instead of presenting either action as successful.Result: The file menu is open and both New file and Duplicate are visibly disabled. The document is unchanged.

Transcript

1. Recognize unavailable file actionsOpen the file menu. New file and Duplicate are disabled in Editor v2, so use the Projects workflow described in Help.

Download the tutorial videoDownload English captions

Prerequisites

• Keep the file open while you diagnose a save problem.
• Record the exact visible message and whether the file is local-only or project-backed.
• Check that you are signed in to the intended account and project.
• If Export as JSON is available, create a backup before reloading or importing a replacement document.

Steps: recover from read-only mode

1. Look for a read-only message and disabled editing controls.
2. Confirm that you opened the intended project, not a shared view or an older local copy.
3. Check the signed-in account. If the file belongs to another workspace, switch only after protecting any local changes.
4. Ask a project manager for edit access when your role is can view.
5. Reopen the project after the permission change and confirm that a small, reversible edit can be made and saved.

Do not try to bypass read-only mode by repeatedly invoking shortcuts or disabled controls. Permission changes must come from the project access settings.

Steps: recover from a save problem

1. Stop making new edits and keep the tab open.
2. Check the save indicator and any visible error message.
3. Restore the network connection for a project-backed file, then retry the save if a retry action appears.
4. If the file is stored locally, make sure the browser still allows site storage and has free space.
5. Choose Export as JSON as soon as it is available, and verify that a file was downloaded.
6. Only after you have a backup, reopen the project or reload the page.
7. If the project still fails to save, import the backup into a separately created destination rather than repeatedly replacing the only open copy.

An import that replaces a document starts a new history baseline. It is not a substitute for a backup you can identify outside the editor.

Steps: install an available update safely

1. When the Update ready card appears, finish or cancel any live drag, resize, drawing, or text edit.
2. Wait for the file’s save state to settle.
3. Choose Restart & update.
4. If every open editor can finish saving, Designful activates the update and reloads.
5. If a file cannot be saved, the update stays on hold and shows a recoverable error instead of forcing a reload.
6. Choose Later when you cannot safely stop. The update can be applied on a later launch or prompt.

If update activation fails, keep the document open, export JSON, restore connectivity, and retry. Do not clear site data while it may contain the only local copy of a file.

Recovery

• Wrong account or role: protect local work, sign in to the correct account, reopen the project, and confirm access before editing.
• Offline project: stay on the open page, restore the connection, and wait for the save state. Export JSON when available.
• Local storage warning: export JSON immediately and move the file into reliable project storage when possible.
• Rejected import: the current document should remain unchanged. Check that the file is a supported Designful export and try the correct file.
• Update will not restart: resolve every open editor’s save error or close only the documents that are safely backed up, then retry.
• Missing font or degraded import: keep the report details, provide the font or rebuild the affected layer, and review the result before export.
• Disabled action with an explanation: compare it with the current-limit table below. A disabled current-limit control is expected behavior, not a failed save.

Current Editor v2 limitations

These six controls are intentionally unavailable in the current version of Editor v2. Do not rely on them during recovery or record them as completed steps.

Unavailable action	What to do instead
New file inside the editor	Create a file from the Projects page, then open it in Editor v2.
Duplicate current file inside the editor	Use a duplication action outside the editor when your workspace provides one. Otherwise export JSON, create a separate destination from Projects, and import the backup there.
Follow collaborator	Use presence to see who is in the file and coordinate the canvas location manually. Editor v2 cannot follow another person’s viewport.
Copy invite/share link	Invite by email, or use a project-sharing action outside Editor v2 when one is available. The disabled control cannot copy a usable link.
Name cloud version	Use available history entries for short-term recovery and export a clearly named JSON backup for a durable checkpoint. Editor v2 cannot name a cloud version.
Add interaction in the Prototype panel	Choose Connector in the toolbar and create the connection directly on the canvas. The Prototype Add interaction button remains unavailable.

Other controls can also be unavailable because the file is read-only, local-only, not project-backed, or missing the required selection. Read the visible reason before deciding that you have reached a product limit.