Org Migration Readiness

During an org migration, your org moves from one instance to another. If you follow our best practices, this maintenance should be seamless. Below are some frequently asked questions regarding org migrations. Pre & Post org migration checklists attached.


Frequently Asked Questions

What actions do I need to take to prepare for an org migration? What will happen if I don’t follow Salesforce Infrastructure Best Practices?
If you are not following our best practices outlined on the Plan and Prepare for Org Maintenance and Releases site, your end users may not be able to access Salesforce after the maintenance is complete.
In order to avoid unintended service disruptions, you may need to take the following actions:
i. Enabling My Domain (NOTE: My Domain is required for customers that have requested the org migration.), and if you have any hard-coded references (for example, na1.salesforce.com) make sure that you update them to relative URLs (for example, login.salesforce.com or your My Domain subdomain) prior to the org migration.


Will an org migration impact Live Agent?
It's possible. During an org migration, your org’s instance name changes. When this happens, the URL you use to access Live Agent/SOS changes. Chat clients and deployment code supplied by Salesforce react to this change and appropriately forward HTTP requests to the new endpoint, but some third-party or custom applications, including Live Agent custom REST clients, may not. These custom applications will not be able to find your account on your previous instance and will likely fail.

To minimize impact to your Live Agent/SOS implementation, follow best practices and ensure your Live Agent custom REST client can properly redirect requests to a new instance of the Live Agent service following any maintenance involving a move for your org. The best method to avoid these issues with your custom client (which, again, will not automatically direct requests to the correct endpoint) is to handle the SwitchServer response and use the 'newUrl' property for the request that resulted in this response and all subsequent requests thereafter. For more information on updating your custom client and testing, read the, How to update your Live Agent custom client when your org instance changes article. This will ensure your custom client will not encounter issues after a site switch, and will provide you ample time to later update the endpoint used from the start of its execution.

For more information about Live Agent endpoints and what is meant by hard-coded Live Agent references, review the article, Live Agent server (endpoint URL) has changed and now Live Agent Chat is no longer working.

Site Switch Readiness

What is a Site Switch?

Each Salesforce instance is built and maintained in two geographically separate locations. An instance is actively served from one location (the active site) with transactions replicating in near real-time to the other completely redundant location (the ready site). This infrastructure model allows us to switch the location of the active site for maintenance, compliance, and disaster recovery purposes, which is referred to as a site switch.

During site switch instance would remain the same instance however will be supported from the secondary data center. During Site switch org will be in read only mode for about an hour.

 

Email IP addresses Whitelist -

https://help.salesforce.com/articleView?id=000355539&type=1&mode=1

http://pages.mail.salesforce.com/gettingstarted/org-maintenance-releases/

 
Important Actions

A. Subscribe to Trust Notifications to know when site switches happen.

B. Follow Salesforce infrastructure best practices by not restricting access to Salesforce IP ranges, removing hard-coded references, and by setting your DNS timeout value to 5 minutes (default setting).

C. Customers with Live Agent/SOS custom clients should ensure those clients can properly handle redirects to the new active site, otherwise a disruption to your Live Agent service can occur. The best method to avoid these issues is to handle the SwitchServer response and use the 'newUrl' property for the request that resulted in this response and all subsequent requests thereafter.
Frequently Asked Questions


1. How does Salesforce communicate a site switch?

Planned site switches are posted to the maintenance calendar on our Trust site at status.salesforce.com. If we need to perform a site switch during an incident to bring an instance back online, the incident record on status.salesforce.com will be updated to reflect that information. Sign up for Trust Notifications regarding your instance to receive maintenance notification emails (reminders, starting, updates, and completed) as well as incident notification emails (new, updates, resolved, and root cause). See the Trust Notification User Guide for more information on how to sign-up for these emails.

2. How long does a site switch take?

Currently, site switches can take approximately one hour to complete. As we improve our operational processes through practice and reiteration, our goal is reduce this window. For planned site switches, we post the anticipated site switch activity window to Trust.

3. Can I opt out of a site switch?

Individual orgs cannot be opted out of a site switches. Due to the multi-tenant architecture of our infrastructure, all orgs on the instance must undergo a site switch at the same time.

Planned site switches are only scheduled during preferred system maintenance windows. We ask that you plan maintenance activities for your Salesforce org (software upgrades, integration changes, etc.) outside of the preferred system maintenance windows.

4. Will I be able to access my org during a site switch?

During planned site switches, your org should be available in read-only mode for the duration of the site switch activity unless otherwise stated. If, for any reason, read-only mode will not be available, the maintenance record on Trust will be updated to reflect the expected impact to availability.

5. What actions are required to prepare for a site switch?

If you already follow our infrastructure best practices by not restricting access to Salesforce IP ranges and setting your DNS timeout value to 5 minutes (default setting), a site switch should be seamless to your users.

Otherwise, if you are restricting access to certain IP ranges or data centers, then update your network settings to include the complete list of Salesforce IP ranges in order to avoid any unintended service disruptions following a site switch. And if you control your DNS timeout values set, then you may need to refresh your DNS cache and restart any integrations following the maintenance.


6. How does a site switch impact previously scheduled activities (weekly exports, Apex jobs, etc.) and Apex callouts?

Ongoing activities will be paused prior to the site switch and resumed following the site switch. Activities scheduled during the site switch will start following the site switch.

A small subset of Apex, Batch Apex, REST API, SOAP API, and Bulk API jobs started prior to the site switch may return an error following the maintenance window. If you receive an error resulting from a previously scheduled job following the maintenance window, restarting the job will return the expected results. We recommend rescheduling large or long-running jobs after the site switch completes for the most seamless experience.Apex callouts to external services will continue to execute during the maintenance, and since these frequently result in follow-up DML calls to the Salesforce application, you may experience issues with intended program flows as the application will be in read-only mode. We recommend preventing these callouts from executing in read-only mode. For more information on how to prevent these callouts, see Apex Callouts in Read-Only Mode.


7. How does a site switch impact Web-2-Lead, Web-2-Case, and Email-2-Case activities?

Web-2-Leads, Web-2-Cases, and Email-2-Cases that occur during the site switch will be queued and processed following the completion of the site switch.


8. Will a site switch impact Live Agent?

Yes. During a site switch, your org’s active site gets switched to the ready location, and the ready site gets switched to the active location. When this happens, the URL you use to access Live Agent/SOS changes. Chat clients and deployment code supplied by Salesforce react to this change and appropriately forward HTTP requests to the new endpoint, but some third-party or custom applications, including Live Agent custom REST clients, may not. These custom applications will not be able to find your account on your previous instance and will likely fail.

To minimize impact to your Live Agent/SOS implementation, follow best practices and ensure your Live Agent custom REST client can properly redirect requests to a new instance of the Live Agent service following any maintenance involving a move for your org. The best method to avoid these issues with your custom client (which, again, will not automatically direct requests to the correct endpoint) is to handle the SwitchServer response and use the 'newUrl' property for the request that resulted in this response and all subsequent requests thereafter. For more information on updating your custom client and testing, read the article, How to update your Live Agent custom client when your org instance changes. This will ensure your custom client will not encounter issues after a site switch, and will provide you ample time to later update the endpoint used from the start of its execution.


For more information about Live Agent endpoints and what is meant by hard-coded Live Agent references, review the article, Live Agent server (endpoint URL) has changed and now Live Agent Chat is no longer working.


9. How does a site switch impact ongoing sandbox refreshes?

Sandbox refreshes that are not completed prior to the site switch will be stopped. The sandbox refresh will restart (not resume) following the site switch. In addition, customers will not be able to initiate a sandbox refresh during the site switch.

Email2Case Setup/Troubleshooting

Email2case sfdconestop demo video-

When emails are sent to the email to case address by a customer two cases being created.

Duplicate cases being created in Salesforce by Email-to-Case can be due to a series of reasons: a workflow rule, an error with the setup on the email server, inaccurate forwarding to the email services address, or the organization recently switched to On-Demand Email-to-Case but the Agent has not been deactivated.

Try the following to narrow down the cause:

1. Check all Process Builder/Flow to ensure that there is not an inadvertent workflow that was created to cause the duplicate cases.
If no Process Builder/Flow are causing the duplicates then proceed with testing and replication.

2. Check to see if you can replicate the issue with both the email address that is customer-facing as well as the service address (the service address is the long address that Salesforce generates when creating a new routing address):
First, attempt to duplicate the results by sending an email to the email address that customers are using. (This should trigger a dup, but note that it can be intermittent.)
Next, send an email directly to the email service address that the emails are being forwarded to and see if this causes the creation of a duplicate. More often than not, when emailing the service address directly you will find that no duplicate cases have been created.
Create an Email Snapshot to see how many emails are received in the org. If you capture two emails, then email-to-case is working as expected, since two emails will generate two cases. For more, please review Troubleshoot Inbound Email Errors with Snapshots
If duplicate cases were created when sending emails to the email address but not to the email service address, it could be that a setting on the email server is causing the duplication. For example, the redirecting rule on the email server is not set correctly, that the email address is part of a cc list, etc. In this instance, the email administration team needs to get involved and provide help by looking into the forwarding of emails and any related settings in place on the email server. Somewhere prior to forwarding to the service address, the email is being duplicated and two emails are being sent to Salesforce.

3. Finally, ensure the email-to-case agent is no longer active. If both the agent and the on-demand version of email-to-case are enabled, and using the same email address, this can cause both to create a new case.

4. Analyze email snapshot headers using http://mxtoolbox.com/NetworkTools.aspx

See Also:
Troubleshooting with Inbound Email Snapshots
Defining Email Service Addresses
Configuring Routing Addresses for Email-to-Case and On-Demand Email-to-Case

Deferred Sharing Rule Recalculation - Deployment Impact

When you deploy Sharing Rules via the Metadata API or Change Sets, sharing recalculation is run to update User access to records. For larger organizations, this recalculation might take a significant amount of time even after the deployment has been successfully performed. Here's how can you minimize the impact caused by Sharing Rule deployment.



Enable Deferred Sharing Rule Recalculation or Parallel Recalculation

Deferred Recalculation lets you apply sharing rule changes at a later time after you create or edit them.
Parallel recalculation takes advantage of multiple threads to speed recalculation of each object. .
To monitor your deployments done via the Metadata API:
In Classic:

1. Go to your name | Setup.
2. Click Deploy | Monitor Deployments.

In Lightning:
Go to Setup
Click on Environments under Platform Tools in the left hand pane
Click Deploy | Deployments StatusTo monitor your deployments via Change Sets:

The outbound change set page will show the results of the deployment, and an email notification will be sent out. If you notice that your deployment is successful but you are experiencing sharing access issues, you can take steps to mitigate them.

To monitor Sharing Rule recalculations running in parallel mode:
In Classic
1. Go to your name | Setup.
2. Click Monitoring | Jobs | Background Jobs.

In Lightning:
Go to Setup
Click on Environments under Platform Tools in the left hand pane
Click Jobs | Background JobsParallel recalculation jobs are listed together with other background processes, including a percentage estimate of the recalculation progress.

Good to know: Before you contact Salesforce Support to have these features enabled, check out Considerations Before Making Org Wide Sharing Changes, Deferred Sharing Rule Recalculation, and Parallel Recalculation.

Bulk API V1/V2

Please do continue to like, share and subscribe sfdconestop Youtube channel, if you find the Salesforce tutorials(100+ Video's) to be informative!!
▶️Subscribe:  https://www.youtube.com/c/sfdconestop
👉 https://sfdconestop.blogspot.com/
👀 Follow us on Linkedin : https://www.linkedin.com/company/sfdconestop
 

Now generally available in Winter ’18 (API version 41.0), Bulk API v2 brings the power of bulk transactions from Bulk API v1 into a simplified, easier-to-use API.

Starting summer20 bulk api can now process 15000 batches against to earlier 10000 batches
 Your organization can process 15,000 batches in a 24-hour period. If bulk jobs page doesn't load add the suffix to the url /750?job_info_only=true

Bulk API v2 lets you create, update, or delete millions of records asynchronously, just like Bulk API v1, but offers the following core improvements:
Bulk API v2 uses the same REST API framework as other Salesforce REST APIs. You can use OAuth authentication just like any other Salesforce REST API and take advantage of features like CORS (cross-origin resource sharing) support.
Bulk API v2 does away with the need to manually break up data into batches. Simply submit jobs with the full set of records, and Salesforce automatically determines the most efficient way to batch the data.
Bulk API v2 simplifies the basic daily limits. Instead of having limits based on the number of Bulk jobs and batches, you’re simply limited to a maximum number of records (100 million) per 24 hour period.

Bulk API v2 also has a number of new features that aren’t available in Bulk API v1, but more on that later.

Additional v2 Features

Bulk API v2 goes beyond Bulk API v1 and offers some additional features to make your life easier. These include:
When creating a new job, you can also include the job data in the same request, using a multi-part request. This is limited to smaller sets of records (up to 20K characters).
You can specify different column delimiters and line endings for your CSV data, including:
backquotes, carets, pipes, semi-colons, and tabs for delimiters (instead of commas)
carriage-return & linefeed line endings (instead of just linefeeds)
You can get a list of all Bulk API jobs in your org (active and completed) and use query parameters to filter this list. For example a GET request to /services/data/vXX.X/jobs/ingest?concurrencyMode=parallel will return a list of all jobs in your org using parallel concurrency mode for processing.

Note that you can’t do Bulk queries in Bulk API v2 yet.

Bulk API v2 reduces the amount of code you have to write and gives you more options on how to process your data. Plus, it simplifies data limits, so you can spend less time worrying about how much data you can work with, and spend more time actually running your integration jobs. Consider taking the time to switch over to using Bulk API v2 if you’re using v1, and your code will be slim and trim in no time!
Further resources

For more information on Bulk API v2, see:

Bulk API 2.0 Developer Guide

https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asynch/queries.htm.

https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asynch/bulk_common_limits.htm

https://developer.salesforce.com/docs/atlas.en-us.api_asynch.meta/api_asynch/how_requests_are_processed.htm Bulk API unit of the API Basics Trailhead module

sfdoncestop youtube over 70 videos - https://www.youtube.com/c/sfdconestop

Salesforce Governor limits

Below are the Pre transaction limits
Description Synchronous Limit Asynchronous Limit
Total number of SOQL queries issued (This limit doesn’t apply to custom metadata types. In a single Apex transaction, custom metadata records can have unlimited SOQL queries.) 100 200
Total number of records retrieved by SOQL queries 50,000
Total number of records retrieved by Database.getQueryLocator 10,000
Total number of SOSL queries issued 20
Total number of records retrieved by a single SOSL query 2,000
Total number of DML statements issued 150
Total number of records processed as a result of DML statements, Approval.process, ordatabase.emptyRecycleBin 10,000
Total stack depth for any Apex invocation that recursively fires triggers due to insert, update, or delete statements 16
Total number of callouts (HTTP requests or Web services calls) in a transaction 100
Maximum timeout for all callouts (HTTP requests or Web services calls) in a transaction 120 seconds
Maximum number of methods with the future annotation allowed per Apex invocation 50
Maximum number of Apex jobs added to the queue with System.enqueueJob 50
Total number of sendEmail methods allowed 10
Total heap size 6 MB 12 MB
Maximum CPU time on the Salesforce servers 10,000 milliseconds 60,000 milliseconds
Maximum execution time for each Apex transaction 10 minutes
Maximum number of unique namespaces referenced 10
Maximum number of push notification method calls allowed per Apex transaction 10
Maximum number of push notifications that can be sent in each push notification method call 2,000

Capture and debug network traffic with Fiddler

The steps below should be followed when you experience performance issues with Salesforce and only when instructed by a Technical Support Engineer. The steps below might be slightly different based on the version of FiddlerCap you are using. For specific questions about how to use this software, please contact FiddlerCap Support.
To do this, we will use a tool, called Fiddler (Not a Salesforce product). Fiddler is a tool for analyzing HTTP and HTTPS (must be enabled from within the app) transactions. This program is a simple-to-use version which can save logs which you can send back to the support team.

In order to install this program, you will need Administrative rights on your local machine. Please consult your IT department if you are unsure, or experience problems installing the application.

Resolution

If you're working with a Salesforce support agent , they can request a capture of network traffic to help with troubleshooting. These can be helpful for support to diagnose issues such as network performance, proxy and browser issues, Single Sign-on, or Integration troubleshooting.

1. Download Fiddler 4 on the local machine
2. Complete the installation and run the application
3. In Fiddler, from the top menu click on Tools | Options | HTTPS |Capture HTTPS CONNECTs
4. Check the box for Decrypt HTTPS traffic and agree to any prompts to install the needed certificate for https decryption
5. Select "Ignore Server Certificate errors" and click on ok to exit out of the Fiddler options.
6. Ensure Capture traffic is selected under the File menu or press F12
7. Run the application or processes that needs debugging and do regular work until the issue seems to have re-occurred.
8. In Fiddler navigate to File | Save | All sessions and save them as a .saz file
9. Close Fiddler
10. Compress and zip the file and attach to the support case along with the information the exact time the issue occurred. You can also email it directly to the support rep you are working with.

* To compress the file, locate the file in the folder after you saved it and then right click on it and click on Send to | Compressed (Zipped) folder

Lightning Component Best Practices

Lightning Components run at the client-side, in a single page (where they are created and destroyed as needed), and alongside other components that work on the same data. In this blog post, we discuss how these characteristics impact performance, and review a list of best practices to optimize the performance of your Lightning Components.

https://developer.salesforce.com/blogs/developer-relations/2017/04/lightning-components-performance-best-practices.html

Data Migration Best Practices

https://help.salesforce.com/articleView?id=Best-Practices-for-Loading-Data&language=en_US&r=https%3A%2F%2Forg62.my.salesforce.com%2F&type=1

How to Capture HAR file and Analyze

Please do continue to like, share and subscribe sfdconestop Youtube channel, if you find the Salesforce tutorials(80+ Video's) to be informative!!
▶️Subscribe:  https://www.youtube.com/c/sfdconestop
👉 https://sfdconestop.blogspot.com/
👀 Follow us on Linkedin : https://www.linkedin.com/company/sfdconestop
 

Create and view HAR files in supported browsers

Chrome

1. Go to the page where you're experiencing slowness.
2. Press F12 on your keyboard.
3. Click the Network tab in the diagnostic window.
4. Click on the link/button/tab to have the problem page or action load in the main window.
5. After the page loads, you should see some information and graphs in the diagnostic window. If the slowness was seen during this page load, Right-click in the diagnostic window and Save as HAR with content.
6. If you need to preserve the logs for multiple page loads, there's a 'preserve log' checkbox below the tabs.
7. Press F12 to remove the diagnostic window.


Internet Explorer


1. Press F12 on the keyboard.
2. You should see a component appear on the bottom of the screen.
3. Go to the Network tab in this component and press the green triangle (Play button)
4. Reproduce the issue.
5. To save, click the red square (stop button.) Directly to the right you will see a disk icon with an arrow on it.
6. Click this icon and save it.
7. IE only offers options to export as an XML or CSV file. Either format is fine. CSV can be viewed via Excel and XML can be viewed by any tool that can read HTTP Archive files, such as the Chrome extension, 'HTTP Archive Viewer.'


View the HAR file log

1. Go to the HAR viewer.
2. Uncheck: Validate data before processing? (Otherwise, an error may occur.)
3. Drag the HAR file inside 'Preview' box.

 

Capture and debug network traffic with Fiddler

 

Row Lock - Record currently unavailable errors

Please do continue to like, share and subscribe sfdconestop Youtube channel, if you find the Salesforce tutorials(100+ Video's) to be informative!!
▶️Subscribe:  https://www.youtube.com/c/sfdconestop
👉 https://sfdconestop.blogspot.com/
👀 Follow us on Linkedin : https://www.linkedin.com/company/sfdconestop
 

When a record is being updated or created, we place a lock on that record to prevent another operation from updating the record at the same time and causing inconsistencies on the data.

These locks normally last for a few seconds and when the lock is released, other operations can do whatever processing they are supposed to do on the record in question. However, a given transaction can only wait a maximum of 10 seconds for a lock to be released, otherwise it will time out.


Common Scenarios that prevent unlocking record

a. Email-To-Case

When an email is processed by email-to-case, triggers on the email message object or related objects (i.e the parent account) will attempt to lock those records for processing. If another process is holding a lock on these records and the processing of the email has to wait for more than 10 seconds, a timeout will occur and you will see this error.
b. Apex Triggers/API

Assume there is an After Insert Apex Trigger on Tasks, and it runs for about 14 seconds while doing some processing. This trigger will run when a task is created. When tasks are created and are related to an Account, we place a lock on the parent Account while the task is being created. This means that the account cannot be updated while the task creation is in progress.
Reduce using Locking Statements.

Scenario:
User A imports a task via the data loader and assigns it to an existing account record. When the task is inserted, the apex trigger is fired.
Just 2 seconds after User A starts the insert via the data loader, User B is manually editing the same account record the task is related to.
When User B clicks Save, internally we attempt to place a lock on the account, but the account is already locked so we cannot place another lock. The account had already been locked by the creation of the Task.
The 2nd transaction then waits for the lock to be removed. Because the task takes about 14 seconds to be created, the lock is held for 14 seconds. The second transaction (from User B) times out, as it can only wait for a maximum of 10 seconds.

In this case, user B would see an error on the screen similar to the ones mentioned above. Apex Tests can also incur locks if run against production data​.

c. Bulk API

Inserting or updating records through the Bulk API can cause multiple updates on the same parent record at once, because the batches are processed in parallel. For example, if two batches are being processed at the same time and the two of them contain records pointing to the same parent record, one of the batches will attempt to place a lock in the parent record, which can lead to the other batch throwing a "unable to lock row" error as the batch was not able to get a lock within 10 seconds.

To prevent this, you can do either of the following:
Reduce the batch size
Process the records in Serial mode instead of parallel, that way on batch is processed at a time.
Sort main records based on their parent record, to avoid having different child records (with the same parent) in different batches when using parallel mode.
For these type of scenarios, it's also highly recommended that you become familiar with the guidelines found on the article


d. Master-detail Relationship

If a record on the master side of a master-detail relationship has too many child records (thousands) you are likely to encounter these errors as well, as every time you edit the detail record, the master record is locked. The more detail records you have, the more likely that these will be edited by users, causing the parent record to be locked.

To prevent this issue you can move some child records to another parent, as to reduce the amount of child records attached to a single parent record.
Record Level Locking is a common scenario which can be reduced.


Troubleshooting:
1. You can enable Debug logs for the user who is facing the error , to find the offending trigger/flow/ValidationRules/ causing the issue.
2. Check for any dependent background jobs that are running on the same object. If there is any, try to pause the jobs and then perform the actions to reduce row locks.

Performance testing Practices

Performance Testing Best Practices-

https://trailhead.salesforce.com/en/users/officialblaze/trailmixes/develop-your-performance-testing-strategy

 

https://salesforce.vidyard.com/watch/Fk6EkAPz6P4btmU8SQBfoS

https://help.salesforce.com/apex/HTViewSolution?urlname=Performance-testing-FAQs&language=en_US

Sandbox Refresh Preview/non Preview Recommendations

Sandbox Instances are split up in two groups – Preview and Non-Preview. Preview Instances are instances which get upgraded to the newer version of Salesforce before Production Instances (e.g. NA2, EU1, AP0) and Non-Preview Instances are upgraded towards the end of a Major Release along with the majority of Production Instances. 

Review detailed video here -

 

You can key in your instance name like cs87 at the instance of the below url to understand what action to be take to stay in preview/non preview mode-

Sample format -
https://sandbox-preview.herokuapp.com/sandbox/cs87

For multi sandbox instances -
https://sandbox-preview.herokuapp.com/sandbox/cs87,cs88,cs89,cs90

Q: Is it possible to move my sandbox that received the release preview off the preview without a refresh?

A: No, in order to move a sandbox off of the release preview you will need to submit a refresh to direct the copy to a non-preview instance.

There are no exceptions and a refresh is always required in this circumstance because the preview upgrade is applied to the entire instance and not at the org level which is why a refresh is required to move the sandbox currently located on a preview instance to non-preview instance.


Q: Is it possible to upgrade my sandbox to the preview after the preview release date has passed?

A: No, since your production environment is still on the current release it is not possible to move an existing or refresh a new sandbox copy onto the release preview. The release version of a sandbox will always match the version of its production organization at the time of the copy.

This is why the sandbox preview window is important because it is designed to allow you to direct copies to sandbox instances that will be receiving an early upgrade or preview of the next release. The preview instances are all upgraded on a specific date. The only way to have sandbox on the release preview is for the refresh to be completed with the sandbox located on a preview instance so it can be upgraded with the instance.

If the preview upgrade date has passed it is no longer possible to direct copies or move a sandbox onto the release preview. The next opportunity to refresh a sandbox to the next major release will be after your production instance has been upgraded.

Should you need to test in a preview org, the only recommendation is to sign up for a pre-release org. The sign up link is typically posted in the Salesforce Blog entry for each major release.


Q: Is it possible to refresh my sandbox and keep it on the release preview if production hasn't been upgraded to the next release yet?

A: No, since your production instance and the sandbox copy's target preview instance are on different release versions this is not possible from an architectural and versioning standpoint.

There may be alternative means to achieve the same goal as a refresh. For example, to move application changes to the sandbox, consider using Change Sets, the Force.com IDE or the Force.com Migration Tool to migrate your metadata. If it is a matter of bringing additional information input since the refresh you should be able to do so by utilizing the API (Apex Data Loader) to extract the data you need for testing from production and then import it into your sandbox.

Full copy Sandbox Refresh best practices -

• Uncheck “Include Chatter Data”
• Uncheck “Include Field Tracking History Data”
• Use Sandbox template

Instance Refresh Readiness

In order to prepare for your organization’s continued growth, we occasionally need to perform an activity, called an instance refresh, where we upgrade the infrastructure supporting your instance in our data centers. Following the maintenance, your instance will move to a new data center, and the name of your instance will change. This will enable us to continue to provide organizations with the same levels of performance they have come to expect from Salesforce.

For example if your org is on NA1 instance post instance refresh your org would move to NA2. 


If you follow salesforce best practices, this maintenance should be seamless. Below are some frequently asked questions regarding instance refresh maintenance.

https://help.salesforce.com/articleView?id=Instance-Refresh-Maintenance-FAQ&language=en_US&r=https%3A%2F%2Forg62.my.salesforce.com%2F&type=1

How to prepare for instance refresh video -
https://salesforce.vidyard.com/watch/gmdRR8QbUA44bVyHNViA37