ACTION MAY BE REQUIRED: Prepare for the EU11 Instance Refresh happening on August 18


As an admin of a Salesforce org on the EU11 instance, we would like to notify you of an upcoming instance refresh maintenance.

In order to prepare for your organization’s continued growth, Salesforce occasionally needs to perform an activity, called an instance refresh, where they upgrade the infrastructure supporting your instance in their data centers. This will enable Salesforce to continue to provide your organization with the same levels of performance.

Following this maintenance, your instance will move to another data center within the European Economic Area, and the name of your instance will change. Salesforce will inform you of your instance’s new name (via email) approximately six weeks prior to the scheduled maintenance window. This will either be the EU17 or EU18 instance.

Do I need to take action?

We have reviewed the information provided by Salesforce and have come to the conclusion that you only need to take action if you reference the instance in for example custom buttons, in custom links in email templates or if you retrieve data like jobs, campus events and contacts via the webservice as described in this article. Make sure other parties, for example intranet, also perform the necessary change if applicable.

The endpoint you currently use to retrieve the data via the webservice, will probably refer to the instance EU11. Since this name will change, you need to change the endpoint.

Getting the correct end-point

It is possible to change "EU11" to the new instance name (which is not known yet) after the refresh has been completed. However, you can and probably should use the custom domain that applies to your org. See this article on setting up a domain if this is not yet set up for your org.

You can find the custom Salesforce domain in Salesforce Set-up under Domain Management. See this picture:

The custom domain looks like this in most cases: "connexys-<4 numbers>". The soap address will then look like this:

<soap:address location=""/>

The advantage of pointing the soap address to your custom domain is that in case of a future instance refresh or org move to another instance there will be no impact on your interfaces.



The original email:

Have more questions? Submit a request


Powered by Zendesk