The Salesforce Spring ‘16 release is quickly approaching and soon you'll be able to take advantage of exciting new features and functionality! If you are a Sandbox customer, you have the opportunity to get early access to Spring ‘16 in your Sandbox and test new customizations and features before your production organization is upgraded.
The Sandbox Preview window for Spring ‘16 is scheduled to begin January 8, 2016. If you would like your Sandbox organization to take part in the Spring ‘16 Preview, your Sandbox must be active on a preview instance by January 8, 2016 to take part in an overall instance upgrade.
Please read carefully and follow the instructions in the next section for specific information on how to handle each of your Sandboxes. In most cases, you will not need to do anything because your Sandbox is already on a preview instance. But you may need to take action by January 1, 2016 in order for your Sandbox to take part in the Spring ‘16 Preview
General Information about the Sandbox Service:
From the time your Production Instance (e.g. NA2, EU1, AP0) was upgraded, all Sandbox creation and refresh requests will be routed to a Sandbox instance that will be upgraded for the preview. We will continue to route these requests to Preview Sandbox Instances until January 1, 2016.
Starting January 2, 2016, all creation and refresh requests will be routed to non-preview instances until your production instance is upgraded to Spring ‘16.
You have from now until January 1, 2016 to decide if you would like your Sandbox to take part in the Spring ‘16 Preview. Follow the steps below for each Sandbox org that you have.
Note: If you have a full Sandbox, be mindful of the 29-day refresh policy and plan accordingly.
I need to create a new Sandbox – What are my options?
I have an existing Sandbox – What are my options?
1) Determine your Sandbox instance
To determine which instance your Sandbox is on, log into your production org and navigate to your Sandbox List page (Search “Sandbox” in the Quick Find bar on the Setup Home Page).
Determine your Sandbox instance by using the Location column above.
2) Refresh? Or Don’t Refresh? Or Do Nothing?
Once you have located the instance that your Sandbox is on, use the chart below to determine if, when, and what action you should take on your Sandbox.
IMPORTANT — Plan Ahead!
The January 1, 2016 deadline is to cut off requests in an attempt to make sure that all preview requests can be met. Due to the number of requests, we cannot guarantee that a request to create or refresh before the deadline will result in a sandbox org on a preview instance.
The sandbox copy must complete (pending activation or activated) before the overall instance upgrade starting on January 8th, 2016. If there are too many requests or if you have a large full sandbox and did not plan ahead, the request you made may not be processed by the time of the upgrade.
If you have a large full sandbox, please keep in mind how much time it takes to complete your Sandbox refresh to ensure your copy is completed by January 8, 2016. If the sandbox copy does not complete by the upgrade on January 8th, the copy will be restarted to a sandbox instance that remains on the same version as your production instance.
Plan Ahead! - You may need to request your refresh in advance of the January 1, 2016 deadline to ensure it completes by January 8, 2016.
AppExchange Preview Instructions
If you plan to upload and/or install one or more AppExchange packages using your Sandboxes during the Sandbox Preview Window, you should use the chart below to determine your course of action.
If you have additional questions about your Sandbox options in conjunction with the Spring ‘16 release, please contact salesforce.com Customer Support.
Understanding the Preview Window Schedule
In addition to the steps above, use the following graphic to understand what will happen to your Sandbox if you request a new sandbox or refresh an existing sandbox. For example, if your Sandbox is on CS12 and you refresh it after 12 AM PST on January 2, 2016, it will be moved to a non-preview Instance.