Retire a sandbox
Retire sandboxes that are outdated or no longer needed to make room for new Developer Sandboxes in your instance.
Before you begin
Save your work, for example commit it to source control or export update sets.
Role required: admin or sandbox_manager
About this task
You should manually retire sandboxes when your work is complete to maintain a healthy development lifecycle.
Warning:
Because sandboxes are retired automatically after an upgrade or clone, ensure any work that you want to keep is preserved before upgrading or cloning.
- For upgrades, you can restore work from the remote update sets that Developer Sandboxes automatically created from prior sandboxes.
- For clones, you must manually save and restore all work in sandboxes.
- Any custom table configuration changes or fixes must be reapplied after an upgrade. Contact Now Support to open a case.
Procedure
-
Select the more options icon
in the Developer Sandboxes dashboard, and then select Retire sandbox.
Figure 1. Retire a sandbox
Result
After it's retired, the sandbox is no longer available for use. However, you can allocate new sandboxes as needed. For more information, see Allocate a sandbox.