Table of Contents

How Often Can You Refresh a Salesforce Sandbox?

Quick answer

This page answers How often can you refresh a sandbox? quickly.

Fast answer first. Then use the tabs or video for more detail.

Watch the video explanation below for a faster overview.
Game mechanics may change with updates or patches.
Use this block to get the short answer without scrolling the whole page.

Read the FAQ section if the article has one.
Use the table of contents to jump straight to the detailed section you need.
Watch the video first, then skim the article for specifics.

▶

The refresh rate of your Salesforce sandbox depends entirely on the type of sandbox you’re using. Understanding these differences is crucial for effective development, testing, and training within your Salesforce ecosystem. Let’s break down the refresh intervals for each sandbox type:

Developer Sandboxes: These offer the most frequent refresh option, allowing you to refresh once per day. This makes them ideal for rapid development cycles and frequent testing.
Developer Pro Sandboxes: Similar to Developer Sandboxes, Developer Pro sandboxes also have a refresh interval of once per day.
Partial Copy Sandboxes: These sandboxes, containing a sample of your production data, can be refreshed every 5 days. This frequency allows for regular integration and user acceptance testing with realistic data sets.
Full Copy Sandboxes: Offering a complete replica of your production environment, Full Copy sandboxes have the longest refresh interval at every 29 days. Due to the extensive data involved, these refreshes take longer and are typically reserved for major project releases and comprehensive testing scenarios.

Therefore, knowing which sandbox type you have is the most important thing when determining when you will be able to refresh it!

Understanding Sandbox Types and Refresh Intervals

Salesforce offers various sandbox environments to cater to different needs within the development lifecycle. Each type has distinct characteristics, including data capacity and refresh frequency. Let’s delve deeper into each sandbox option:

Developer Sandbox

Purpose: Meant for individual developers working on specific features or components.
Data: Limited data and file storage (200 MB each).
Refresh Interval: Once per day.
Use Case: Ideal for building and testing individual features or small applications in isolation.

Developer Pro Sandbox

Purpose: Similar to Developer Sandboxes but with more storage space.
Data: Larger storage limits than Developer Sandboxes.
Refresh Interval: Once per day.
Use Case: Suited for development tasks requiring slightly more data or complex configurations.

Partial Copy Sandbox

Purpose: Intended for quality assurance (QA), integration testing, and user acceptance testing (UAT).
Data: Includes a sample of your production data, determined by a template.
Refresh Interval: Every 5 days.
Use Case: Effective for testing integrations with other systems and validating new features with realistic data.

Full Copy Sandbox

Purpose: Mimics the production environment for comprehensive testing and staging.
Data: Contains a complete replica of your production data, metadata, and configurations.
Refresh Interval: Every 29 days.
Use Case: Best for regression testing, performance testing, and training users on new releases.

Factors Affecting Refresh Duration

While the refresh intervals are defined, the actual time it takes to refresh a sandbox can vary considerably. Several factors influence the duration of a sandbox copy or refresh:

Number of Customizations: A heavily customized org with numerous custom objects, fields, and code will take longer to refresh.
Data Size: The amount of data in your production org directly impacts the refresh time, especially for Full Copy sandboxes.
Number of Objects: A large number of standard and custom objects increases the complexity of the refresh process.
Configuration Choices: Complex configurations and intricate settings can extend the refresh duration.
Server Load: Salesforce’s infrastructure load at the time of the refresh request plays a role. Refreshes are queued, and higher server load can delay the start time.

What Happens During a Sandbox Refresh?

A sandbox refresh essentially creates a new sandbox by copying the metadata and, depending on the type, the data from your production org. This process has several implications:

Data Overwrite: All data and metadata in the existing sandbox are overwritten with the data from the source org.
User Changes: Manual access changes made in the sandbox are reversed, and user profiles and permissions revert to their production values.
Sandbox-Only Users: Any users created exclusively in the sandbox are deleted.
Org ID Change: The org ID of the sandbox changes with each refresh.

Best Practices for Sandbox Management

To optimize your sandbox strategy and minimize disruptions, consider these best practices:

Plan Ahead: Schedule your sandbox refreshes strategically, taking into account project timelines and testing requirements.
Use Sandbox Templates: Create sandbox templates to define the data and metadata copied during a refresh, particularly for Partial Copy sandboxes.
Communicate Changes: Inform users about upcoming sandbox refreshes and potential disruptions.
Automate Tasks: Utilize automation tools to streamline post-refresh tasks, such as data masking and user setup.
Regularly Refresh: Keep your sandboxes up-to-date to ensure they accurately reflect the production environment.

Salesforce Sandbox FAQs

Here are some frequently asked questions to further clarify the intricacies of Salesforce sandbox refreshes:

Can I cancel a sandbox refresh request?

No, it is not possible to cancel a sandbox refresh request once it has been submitted. The refresh process completely replaces the content of the sandbox.
Does the org ID change after a sandbox refresh?

Yes, the org ID of your sandbox changes each time it’s refreshed. Salesforce updates the new value in relevant locations.
What happens to users after a sandbox refresh?

Sandbox refreshes delete and recreate the sandbox as a copy of the production org. If you created sandbox-only users, they no longer exist. Other users’ profile and permissions revert to their values in the production org.
How long does a full sandbox refresh take?

Full sandbox refreshes may complete within a few hours, but can also take several days or more, depending on the factors mentioned earlier, like level of customization, organization size, and server load.
What is the difference between refreshing and cloning a sandbox?

Refreshing a sandbox updates its content with the latest data and metadata from the source org. Cloning a sandbox creates a new sandbox by copying the data and metadata from an existing sandbox.
Can I refresh one sandbox from another sandbox?

No, you can not refresh one sandbox from another. Sandbox refreshes always pull data and metadata from a source org, typically your production org.
Why can’t I refresh my sandbox?

If the “Refresh” link is missing, it could be due to an expired sandbox license or the refresh interval not having passed. Contact Salesforce Support to confirm.
What is the difference between a Developer sandbox and a Full sandbox?

Developer Sandboxes have limited storage and can be refreshed daily, while Full Sandboxes have the full storage capacity of production and can only be refreshed every 29 days.
How do I enable a sandbox after a refresh?

Refreshed sandboxes that haven’t been activated yet show an “Activate” link next to their name. Click “Activate” to complete the process.
Are sandboxes 100% safe?

While sandboxes are isolated environments, security best practices should still be followed to mitigate potential risks. Be careful when using the sandboxes. Also, while the software or applications that you install inside the Windows sandbox environment remain “sandboxed”, and they all run separately from the host machine, this refers to the Windows sandbox functionality.
What is the main use of a sandbox?

The main use of a sandbox is to provide an isolated environment for testing, development, and training without impacting the production org.
Can sandbox rules override service or interactive program controls in a policy?

Yes, sandbox rules override any controls on the same resources specified by the specific service or interactive program controls in a policy.
What are the benefits of sandbox refresh?

Refreshing a sandbox updates the sandbox’s metadata from its source org. If the sandbox is a clone or if it uses a sandbox template, the refresh process updates the org’s data in addition to its metadata.
What considerations affect the duration of a sandbox copy or refresh?

Several conditions affect the duration of a sandbox copy or refresh. These conditions include, the number of customizations, data size, numbers of objects and configuration choices, and server load. Also, sandbox refreshes are queued, so your copy request doesn’t always start immediately.
What is a sandbox?

A sandbox is an isolated testing environment that enables users to run programs or open files without affecting the application, system or platform on which they run. Software developers use sandboxes to test new programming code. You can learn more about games that utilize sandbox environments at Games Learning Society – https://www.gameslearningsociety.org/.

By understanding the nuances of sandbox refresh intervals and best practices, you can optimize your Salesforce development and testing processes, leading to more efficient and reliable deployments.