What does recovery do?
CoBlocks can keep a project snapshot in this browser. If the server copy is unavailable and a valid local snapshot exists, it can load that copy. This is a safety net, not a full version history.
If your project is recovered
- Save the recovered project to Scratch and download an .sb3 copy straight away.
- Keep the browser profile intact; do not clear extension storage before saving.
- Live collaboration is paused in recovery-only mode. Reopen normally once service is restored.
More detail & reference
Three different kinds of saving
| Layer | Purpose and limits |
|---|---|
| Scratch save / .sb3 download | Your normal saved project and portable backup. Continue to use these during collaboration. |
| Backend snapshot and changes | The server copy and collaboration event stream used to synchronize authorized editors. |
| Local recovery snapshot | A valid project snapshot stored in the extension’s browser profile, scoped to account and project. It is not a cross-device backup or unlimited history. |
When local recovery is used
If the server cannot provide a valid project but this browser has a valid local snapshot, CoBlocks can load that snapshot. It tells you that local recovery was used and pauses live collaboration.
Save the recovered project to Scratch immediately and download an .sb3 backup. Other collaborators are not receiving live changes from this recovery-only editor. Reopen the normal collaboration only after service and access are working again.
Rejected or damaged snapshots
The editor validates loading and attempts to restore the project that was already open if a received snapshot fails to load. Read the displayed error, save a separate local copy of intact work, and check service status before trying again.
Use CoBlocks Revert deliberately
- If available in the active CoBlocks editor toolbar, select CoBlocks Revert.
- Read the confirmation: it resets to the Scratch/My Stuff version loaded before this CoBlocks session.
- Confirm only after backing up any current work you need.
- Use Scratch’s Save now to finalize the reverted project.
Server recovery and retention
The backend uses redundant JSON mirrors and bounded snapshots to recover damaged records. These are operational storage mechanisms, not a user-facing version-history timeline.
The bundled cleanup removes inactive project records after 60 days with no connected clients. Operators may run different policies; ask a custom-server operator about retention and backups.