Sandbox Resync

When a sandbox is created from a Template, the template's definition is cloned into the sandbox at creation time. Subsequent changes to the template do not automatically propagate to existing sandboxes. To bring a sandbox's definition back in sync with the template, an explicit resync must be performed.

Before Resyncing

Be aware of the following consequences of a resync:

• Any workloads in the current sandbox that are no longer defined in the template will be permanently removed.
• Other changes to the sandbox definition that differ from the template will be reverted to match the template.

Review the changes carefully before proceeding.

Resyncing from the Web UI

Click the Resync button on the sandbox page. If critical changes will be applied (such as workload removal), the Web UI will prompt for confirmation before proceeding.

Resyncing via CLI

Run cs sandbox update without additional flags to perform a resync:

cs sandbox update

See Also

• Template — the template that the sandbox is synced back to
• Sandbox — sandbox structure and workloads
• Workload Restart or Rebuild — related operations on individual workloads