Support
Troubleshooting
Resolve saving, history, collaboration, and AI workflow problems without losing pending work.
Changes are not showing as Saved
Keep the project open and read the save message. The Pages section editor applies valid edits automatically after a short pause and when closing or switching sections. Correct any highlighted validation errors, then wait for the project header to show Saved. The editor's Changes save automatically message alone does not confirm that the project has finished saving.
For a connection or session problem:
- Preserve recent text or use the recovery download when offered.
- Restore the connection or follow the sign-in instructions.
- If a reload is required, preserve pending work first, then inspect the current project.
- Reapply only what is still missing and wait for Saved.
Do not clear browser storage before preserving unsaved work. If the same save conflict returns, contact support with the project name, exact message, and what you were editing. We can help identify a stale local draft without deleting the project or its history.
The editor paused after a restore
A workspace restore invalidates older editing sessions so pending changes cannot silently overwrite the restored version. Preserve or download unsaved work when offered, then reload. Compare any recovered notes with the current content before reapplying them.
An older project may also wait for a legacy editing tab to finish before conversion. Finish saving in that tab, close it, and reopen the project in the current editor.
I cannot find History
Open Documentation, Structure, or Pages, then look for History in the main project header. History belongs to each workspace; the overview is view-only. It is separate from the AI compatibility changelog in these docs.
If the timeline is empty, the next saved edit starts it. You can save a milestone now. History does not reconstruct edits from before it was enabled.
A version says Audit record only
Its saved content has expired. The audit entry remains for reference, but cannot be previewed or restored. Automatic versions are available for 30 days; named milestones retain protected versions within the storage allowance.
Removing a milestone's protection uses the version's original date for expiry. See History, milestones, and restore.
A restore failed or a milestone cannot be saved
Finish saving pending edits first. If the workspace changed after you loaded a preview, refresh History and review the comparison again before restoring. Do not retry using an old comparison.
For a milestone, check the count and storage shown in History. Remove protection from an unneeded milestone if you have reached the allowance, understanding that older content may expire immediately.
I cannot find a node or page
Use Fit and the visible zoom controls. In Pages, clear the page search and status filter; the Section library has its own independent filters. In Documentation, clear search to return to the full section outline.
Creation shortcuts work only outside text inputs and editors. Click the canvas or use the visible tool button when a shortcut is being treated as typed text. See Keyboard and canvas controls.
A shared section did not update as expected
Check whether you edited the library definition or a page placement. The definition supplies shared fields, layout, and guidance. Placement titles and statuses are independent. Similar names do not prove that sections share a definition, and older embedded sections may be marked Legacy.
Let valid edits apply, correct any validation errors, then check for Saved. See Pages and reusable sections.
A pattern's preview and fields look different
Patterns and content fields are independent. Renaming or deleting a field keeps the selected preview unchanged. When changing patterns, Keep existing fields changes only the visual pattern; Replace fields uses the new starter structure. For a plain Base block, Clear fields removes the current structure. Cancel leaves both unchanged.
Existing sections and imported seeds are not filled with missing fields automatically. Add fields manually or choose a different pattern to start from its fields. Selecting the current pattern again does not restore fields you removed.
A new-project seed is rejected
Ask the current Skafold Project Assistant to run its bundled validator and return a corrected skafold-project-seed file. Review the validation message shown by Import AI Plan. Errors such as duplicate IDs, missing references, or invalid values must be corrected before import; some warnings can describe intentionally incomplete planning.
For file authors, see AI format reference.
An AI returned an existing-project update file
Bulk files such as skafold-frame-update are no longer supported. Install the current Skafold Project Assistant. Use a computer-use agent for focused edits in the signed-in editor, or ask for precise manual changes.
A substantial rebuild uses a seed to create a separate new project with its own history. It does not overwrite or merge back into the original.
An agent cannot edit the project
The tool needs browser or computer-use controls and access to your signed-in editor. AI Context provides read access to a published snapshot, not editing access. The skill supplies guidance; it does not add missing browser controls or permissions.
Respect read-only controls and any active editing restrictions. If saving fails, preserve pending work and resolve it before continuing. After an interruption, inspect what saved before retrying to avoid duplicates.
AI Context has unpublished changes
Saved project content is newer than the published snapshot. Choose AI Context → Update AI Context in the main header, or publish through Manage AI Context after reviewing the changes.
Presentation-only changes may leave the revision unchanged while marking the snapshot current. Saving the live project and publishing AI Context are separate actions.
An AI cannot read the context URL
Check that the tool can make HTTPS requests and that the complete URL was copied. The link does not use your Skafold login session. A deleted link cannot be restored; create a replacement and update trusted tools and team members.
Do not include the URL in public support requests.
Skafold recommends a newer skill
Download the current plugin or standalone skill from Install Skafold Project Assistant, install it using your tool's supported flow, and start a new task. Website updates do not replace already installed copies. A compatible older seed may still import, but new files should use the current guidance.
You still need help
Contact support with the project name, exact message, and steps that led to the problem. For a file-validation issue, add a reduced, non-sensitive example. Do not include AI Context URLs, passwords, credentials, or private customer data.