Loading

End-of-Support Schedule for Incorrect Instanced URLs in API Traffic

Veröffentlichungsdatum: Mar 13, 2026
Beschreibung

Salesforce is decommissioning the service that supports hard-coded references to an incorrect instance name in API traffic routing. You can test this change starting June 19, 2026. That service stops on a rolling basis shortly after your org gets Winter ’27, starting in August 2026 (sandboxes) and September 2026 (production).

This article details the specific dates that service is decommissioned by Salesforce instance.

 

Enforcement Delay

This release update was previously scheduled to be enforced shortly after Spring ‘26. Due to an unforeseen issue with deploying the enforcement across a group of orgs, Salesforce delayed the enforcement to Winter ’27. The option to test this release update will be available after Salesforce completes its internal testing, which is currently scheduled to end in May 2026.

The UI reflects the new enforcement release with Spring ’26, patch 10. To determine the patch version for your org, go to Trust Status, search for your My Domain name or instance, and then select your instance name.

Lösung

To prevent disruption, update instanced URLs in API traffic to your org’s My Domain login URL. My Domain login URLs don’t change when your org is moved to another Salesforce instance. 

 

Recommended Testing Method: After June 18, 2026

We highly encourage you to use that setting to test this change before it’s enforced with Winter ’27. 

If you enable this change before the related known issue is resolved, SOAP login URLs via Visualforce pages can return a 400 Bad Request error. Salesforce plans to deploy a fix for that issue June 16–18, 2026, so we recommend that you test this change after June 18, 2026.

To test this change, from Setup, in the Quick Find box, enter My Domain, and then select My Domain. Under Redirections, click Edit, and then enable Block API traffic that uses an incorrect instanced URL.

 

 

Enforcement Timeline

Salesforce stops the service that supports incorrect instance names in API calls based on the org’s instance. To get the instance name for your org, see View Instance Information for Your Salesforce Organization.

After Salesforce makes this change, the “Block API traffic that uses an incorrect instanced URL” setting is no longer available on the My Domain Setup page.

Sandboxes

Dates

Sandbox Instances

August 12-14, 2026

CS340, USA4S, USA6S, USA14S, USA16S, and USA18S

September 1-3, 2026

All other sandbox instances

Production and All Other Orgs

Dates

Instances

September 3-5, 2026

USA12 and USA1104

October 5-7, 2026

USA26, USA220, USA1000, USA1106, and USA926

October 12-14, 2026

AP52, AP54, AP56, AP58, AP60, AP62, NA224, NA226, NA232, NA235, NA241, NA245, NA247, NA249, NA251, NA252, NA254, SWE10, SWE100, SWE106, SWE108, SWE112, SWE114, SWE118, SWE12, SWE120S, SWE122, SWE124, SWE126, SWE128S, SWE130S, SWE132S, SWE14, SWE16, SWE18, SWE20, SWE22, SWE24, SWE26, SWE28S, SWE2S, SWE30S, SWE32, SWE34, SWE36, SWE38, SWE40, SWE42, SWE44S, SWE46, SWE48, SWE4S, SWE50, SWE52, SWE54, SWE56, SWE58, SWE60S, SWE62, SWE64, SWE66, SWE68, SWE6S, SWE70, SWE72, SWE74, SWE76, SWE78, SWE8, SWE80, SWE82, SWE84, SWE88S, SWE90S, SWE92S, SWE94S, SWE96S, and SWE98

November 9-11, 2026

All other instances

 

Nummer des Knowledge-Artikels

005228941

 
Laden
Salesforce Help | Article