Refreshing a cloned sandbox updates the sandbox’s metadata and data from its source org. The org ID of the sandbox changes each time it’s refreshed.
Required Editions
| Available in: both Salesforce Classic and Lightning Experience |
| Available in: Professional, Enterprise, Performance, Unlimited, and Database.com Editions |
| User Permissions Needed | |
|---|---|
| To view a sandbox: | View Setup and Configuration |
| To create, refresh, activate, and delete a sandbox: | Manage Dev Sandboxes (Developer or Developer Pro only) or Manage Sandboxes (all sandbox types) |
- If you're refreshing a cloned Developer, Developer Pro, Partial, or Full sandbox hosted on a Hyperforce instance, your sandbox is refreshed using the Quick Clone technology based on availability. The Quick Clone method refreshes your cloned sandbox faster than the legacy method. However, because of resource limitations within the shared infrastructure, sandbox clone refreshes on Hyperforce instances can sometimes default to the legacy method, rather than the faster Quick Clone method. See Best Practices for Salesforce Sandbox Creation and Refresh Times for more information.
- Between the completion of a major release upgrade and the start of the next release upgrade, we attempt to create sandboxes that preview the next release by default. To create non-preview sandboxes during the transition between major releases, contact Salesforce Customer Support to enable this functionality. When this functionality is enabled, you can choose to create non-preview sandboxes during release transitions. See What are Preview and Non-Preview Sandboxes for more information.
- If custom domains are associated with your sandbox, before you refresh or clone it, review Considerations for Custom Domains in Sandboxes.
- A cloned sandbox refreshes from its source org and retains the source org’s sandbox license type. If a sandbox’s source org has been deleted, the clone refreshes from your production org.
- External client apps aren’t included in the update when you refresh a cloned sandbox.
-
From Setup, find and select Sandboxes.
A list of your sandboxes displays. Sandboxes that you can refresh have a Refresh link next to their name.
- Next to the name of the sandbox you want to refresh, click Refresh.
- Review the name and description, and edit them if needed.
-
Review the Create From value, which is the source org for the refresh.
If you don’t want to refresh the cloned sandbox using its original source org, select a different sandbox or your production org.
- If you want to activate your sandbox immediately after you refresh it, select Auto Activate, which means that you don’t receive an activation email.
-
To run scripts after each creation and refresh for this sandbox, specify the name of an
Apex class that extends the
SandboxPostCopyinterface.The Apex class you specify must exist in your source org. See Create an Apex Class and SandboxPostCopy Interface for more information on creating this Apex class.
For sandbox clones, Data Storage and Sandbox Access are non-selectable. Sandbox access is provided to users who have access to the source sandbox.
-
Click Create.
Salesforce starts copying metadata and data to the sandbox.
Refreshing your sandbox can move it to a different Salesforce instance. For example, the sandbox can move from CS40 to CS50. If you’re subscribed to Trust Notifications, check your subscription settings to ensure that you continue to receive updates about unforeseen incidents and planned maintenance that affect your sandbox.
If you didn’t select Auto Activate, an email is sent when your sandbox is ready to activate. If you aren’t a user in the source sandbox, an email notification isn’t sent. Instead, you can monitor the sandbox status in the Sandbox Setup page.