Refresh Your Sandbox
Refreshing a sandbox updates its metadata from the source org. If the sandbox is a clone or if it uses a sandbox template, the refresh process updates the org’s data and its metadata. 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) |
However, because of resource limitations within the shared infrastructure, sandbox refreshes on Hyperforce instances can sometimes default to the legacy method, rather than the faster Quick Create method. See Best Practices for Salesforce Sandbox Creation and Refresh Times for more information.
If custom domains are associated with your sandbox, before you refresh it, review Considerations for Custom Domains in Sandboxes.
The refresh interval for each sandbox environment is calculated from when you request a sandbox creation or refresh.
| Sandbox Type | Refresh Interval |
|---|---|
| Developer | 1 day |
| Developer Pro | 1 day |
| Partial Copy | 5 days |
| Full | 29 days |
-
From Setup, in the Quick Find box, enter Sandboxes, and then
select Sandboxes.
A list of your sandboxes appears. Sandboxes that you can refresh have a Refresh link next to their name.
- Next to the name, click Refresh.
- Review the Name, Description, and Create From values, and edit these values if needed.
-
Select the type of sandbox environment you want.
A table shows the number and type of sandbox licenses available in your org. You can select a different sandbox type to refresh.
If the sandbox you’re refreshing is a clone, this option isn’t available. A cloned sandbox refreshes from its source org and retains the source org’s sandbox license type. If a sandbox’s source org is deleted, the clone refreshes from production.
-
Select the data you want to copy.
- For a Partial Copy sandbox, click Next, and then select the template to specify the data for your sandbox. If you haven’t created a template for this Partial Copy sandbox, see Create or Edit Sandbox Templates.
- For a Full sandbox click Next, and then decide how much data
to include.
- In the Object Data Included field, select All to include all production data, or select Template-based to choose an existing sandbox template. For more information, see Create or Edit Sandbox Templates.
- Choose whether to include field tracking history data. If your production org is on Hyperforce, select the checkbox to include 30 days of field tracking history. For non-Hyperforce production orgs, select an option from the dropdown menu.
- Decide whether to copy Chatter data. Chatter data includes feeds, messages, and topics and is used in many components that affect your sandbox copy.
Decreasing the amount of data you copy can significantly speed sandbox copy time.
- (Optional) To activate your sandbox immediately after you refresh it, select Auto Activate. In this case, you don’t receive an activation email.
- (Developer or Developer Pro only) If you have an available storage upgrade and want to use it, click 400 MB or 2 GB, or change the data storage to its default value.
-
To run scripts after each creation and refresh for this sandbox, specify the name of an
Apex class that extends the
SandboxPostCopyinterface.
Note See Create an Apex Class and SandboxPostCopy Interface for more information on creating this Apex class. -
For Sandbox Access, indicate a public user group that contains the users that require
access to the sandbox (required for Developer and Developer Pro sandboxes).
For Partial Copy and Full sandboxes, you also have the option to select All Active Users. Selecting all users can increase sandbox creation times and impact the login experience.
How you select the public group depends on how many public groups exist in your production org.
- If the production org has fewer than 60 public groups, select the group from the Public Groups dropdown.
- If the production org has 60 or more public groups, enter the group name in the Public Groups field.
For more information on Selective Sandbox Access, see Determine Who Has Sandbox Access.
- Click Create.
- 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 affects your sandbox.
Salesforce starts copying data to the sandbox.
If you didn’t select Auto Activate while refreshing your sandbox, an email is sent when your sandbox is ready to activate.
