---
schema_version: "1"
id: 35c29d0c598f5326d365570dfb6e680a6c84e6668a5ab715c09bdd1892c9d381
title: Refresh a Cloned Sandbox
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/data_sandbox_refresh_clone.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.data_sandbox_refresh_clone.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 0b5bbb8600db6c15f79625bb7fc5cd0a6617f5cf151aae89be6e8902ba1eb815
description: 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.
products:
  - Salesforce Platform
release: "264"
---
# Refresh a Cloned Sandbox

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

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: both Salesforce Classic and Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Professional</strong>, <strong>Enterprise</strong>, <strong>Performance</strong>, <strong>Unlimited</strong>, and <strong>Database.com</strong> Editions</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d13821e75">User Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d13821e75 ">To view a sandbox:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d13821e75 ">View Setup and Configuration</td>

          </tr>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d13821e75 ">To create, refresh, activate, and delete a sandbox:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d13821e75 ">Manage Dev Sandboxes (Developer or Developer Pro only) or Manage Sandboxes (all
              sandbox types)</td>

          </tr>
        </tbody>
      </table>

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-deploy_sandboxes-264-0-0-production-enus/654e51d1-6795-49fe-bd43-b5385950cf4a/images/icon_note.png)

Note Note these considerations for refreshing a cloned sandbox.

- 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](https://help.salesforce.com/s/articleView?id=platform.data_sandbox_what_impacts_sandbox_creation_time.htm&release=264.0.0&type=5 "Although Salesforce can’t speed up the process of creating or refreshing sandboxes, these strategies can help you to minimize sandbox copy 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](https://help.salesforce.com/s/articleView?id=platform.data_sandbox_preview.htm&type=5&language=en_US) for more information.
- If custom domains are associated with your sandbox, before you refresh or clone it, review [Considerations for Custom Domains in Sandboxes](https://help.salesforce.com/s/articleView?id=platform.domain_mgmt_sandbox_custom_domains_considerations.htm&type=5&language=en_US).
- 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.

1. 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.
2. Next to the name of the sandbox you want to refresh, click **Refresh**.
3. Review the name and description, and edit them if needed.
4. 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.
5. 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.
6. To run scripts after each creation and refresh for this sandbox, specify the name of an Apex class that extends the `SandboxPostCopy` interface.
    
    The Apex class you specify must exist in your source org. See [Create an Apex Class](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_develop_create_apex.htm) and [SandboxPostCopy Interface](https://developer.salesforce.com/docs/atlas.en-us.apexref.meta/apexref/apex_interface_System_SandboxPostCopy.htm) 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.
7. 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](https://help.salesforce.com/s/articleView?id=000381874&type=1&language=en_US), 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.

#### See Also

- [Activate Your Refreshed Sandbox](https://help.salesforce.com/s/articleView?id=platform.data_sandbox_refresh_activate.htm&release=264.0.0&type=5 "If you didn’t select Auto Activate while refreshing your sandbox, you must activate your sandbox before you can use it.")