Saved Work And Sharing

What gets saved

Surface	Saved item	Collection
Analyze	Analysis	Analyses
Decide	Proposal	Proposals
Notebooks	Notebook	Notebooks

• Analyses save Analyze context such as lot, snapshot, selected test, brushed dies, wafer focus, and staged what-if limits.
• Proposals save Decide evidence, screening logic, baseline, and disposition review state.
• Notebooks save Python code, lot scope, and an optional pinned snapshot.

For the Analyze walkthrough, see Quickstart. Editing What-If Limits changes an analysis’s scenario; it does not create or approve a proposal in Decide. Follow Proposal Review to attach saved evidence there.

Create a server version

Give new work a meaningful title and choose a personal or shared space. In Analyze, Create Analysis creates the saved analysis; subsequent Save actions add versions. A working copy preserves your edits while navigating between surfaces, but is not itself a saved version.

State	What it means
Working draft / unsaved edits	The current investigation has changes not yet saved as a server version.
Local recovery saved	A checkpoint exists in this browser’s storage. It is not a server save or a backup.
Saved version	A server checkpoint that can be reopened and shared as that version.

Saved analyses remain linked to their lot and pin the snapshot in the saved state. Rebase latest deliberately moves editable analysis context to the latest snapshot; review and Save to record that as a new version. Older versions keep their original snapshot. Start a new analysis to change lots. See Upload And Snapshots.

Recover an unsaved draft

1. Open the toolbar’s hamburger management menu and choose Local recovery.
2. Find the copy by its name, lot, date, and summary. The current checkpoint is marked Active draft; summaries describe selected dies and limits, notebook cells/scope, or proposal evidence. Hover or focus a summary for more detail.
3. Choose the matching lot and Restore. Review the restored state, give it a useful title, and save it to the server if you want to keep it.

Restore creates a separate draft, appends (recovered) to its title, and pins the original snapshot when known. An untitled analysis uses New analysis as that title’s starting point. It does not rename the original or create a server version. The source recovery copy remains available; Discard requires confirmation.

Recovery copies are scoped to the signed-in account and user in this browser. Editable unsaved work is checkpointed after a short pause, or within about 2.5 seconds of continuous editing. Wait for Local recovery saved before closing the tab; changes after the last successful checkpoint can still be lost.

The copy includes saved-state fields such as selected dies, scenario limits, Python code, and attached scope. It excludes cell outputs, running variables, and downloaded analysis datasets. Limits are 8 MiB per copy and 100 copies / 50 MiB per account-user scope. Storage failures are shown rather than silently deleting older copies. Browser clearing, eviction, or private browsing can still remove recovery data: save important work to the server.

Resolve a save conflict

If another editor saved a newer version, your save stops instead of replacing their work. Your unsaved edits remain on screen. Choose the next step deliberately:

• Compare changes shows which fields differ.
• Save my edits as a copy creates separate saved work without overwriting the original.
• Keep recovery and load latest checkpoints your edits locally, then opens the newest version. If local recovery fails, save a separate server copy before replacing your work.

Opening a historical version does not let you overwrite the newest version. Save a separate copy when you want to continue independently from older work.

Opening the same saved item in another tab shows an advisory warning, including whether that tab has unsaved edits. This is not a lock or a substitute for save conflict checks. The local warning covers the same browser origin, realm, account, and user, not other devices. Shared-space presence is also advisory.

Share a version or collaborate in a space

Use a personal space for private work and a shared space for team collaboration. Shared spaces have their own membership and permissions, separate from account roles. See Roles And Access.

A share link opens one saved version read-only, even when its visitor can edit the source item elsewhere. It does not grant shared-space membership. Sharing unsaved edits first goes through the save and conflict checks; the link does not expose a continuously changing draft. Active links per item are capped.

Check the opened share

Older app builds can stall at Preparing exact selection when opening an analysis share. The fix was verified on the hosted demo on 7 September 2026; other installations need their own rollout check. Do not interpret the empty views or zero selected dies as the saved result. Verify that the intended version and its datasets loaded before reviewing it; see the fixed builds and precautions.

Saved items can be active, archived, or controlled. Archived work is removed from normal active work. Controlled work is permanently frozen as a review artifact; use that state only when it must no longer change in place.

Notebook runtimes are separate from saves

For attaching data, running cells, sampling limits, and frame behavior, see Notebook Execution. This section describes what survives a runtime reset, not how to execute a notebook.

Each notebook editor has its own Python runtime, even when two tabs open the same saved notebook. Variables and attached frames are not shared across tabs. A hidden tab releases its idle runtime after about a minute without interrupting a cell already running. Switching workspace or leaving Notebooks also releases the runtime; server idle expiry provides fallback cleanup after a crash.

An idle runtime reset leaves the editor’s code and displayed outputs in place, but variables must be recreated by rerunning setup cells. Those outputs and variables are not part of a document save or local recovery copy.