Workload Restart or Rebuild

A Crafting workload can be restarted or rebuilt in three ways, depending on how much of the workload's state should be preserved:

Restart

A restart is the simplest and fastest operation. It stops all processes and starts them again. All persisted files are preserved — no data is lost.

Use restart when you need to reset running processes without affecting the filesystem.

Refresh Base Snapshot

This operation is only available for workspaces.

Refresh Base Snapshot is used when the base_snapshot field in the workspace definition has been updated and you want to apply the new snapshot to the running workspace. The operation pulls the new base snapshot and discards all current modifications to the root filesystem, except for the directories excluded from the base snapshot (such as /home).

Because most development work involves files under /home (source code, personal configurations, build outputs), refreshing the base snapshot preserves important developer files while updating the system-level environment.

Use this when the platform team or org admin has updated the base snapshot with new tools or system configuration, and you want to pick up those changes without rebuilding from scratch.

Rebuild

A rebuild discards all persisted data of the workload and starts from a new, empty persistent volume. Everything stored in the workload is lost in this operation — this includes all files outside of any snapshots.

Use rebuild as a last resort when the workload's persistent state is corrupted or needs to be completely reset.

See Also