Learning Studio / reference
Checkpoints and version history
Keep an intentional recovery point before making a large change.
Save a checkpoint
Section titled “Save a checkpoint”Open Versions, give the checkpoint a recognizable label, and save it before restructuring or applying a large AI proposal. History includes supported autosaves and pre-change AI/agent snapshots; automatic retention is bounded.
Used AI Assist suggestions appear with an AI Assist label in course history. File versions are separate: open a resource’s History & courses in Files to inspect or restore its bytes. See files and fonts.
Restore
Section titled “Restore”Open a version to inspect it, then use the restore action when you intend to replace the current course with that version. Restore creates a new validated course change. It does not rewrite published Git history or erase the fact that later changes occurred.
After restoration, check the outline, media references, objectives, and learner preview. A historical content snapshot does not guarantee that an independently deleted media file still exists.