Loading

Unable to Deploy an Experience Cloud Site When Source Org Is on a Newer Salesforce Release (Version Mismatch)

Fecha de publicación: May 12, 2026
Descripción

When attempting to validate or deploy a change set that contains Experience Cloud (formerly Digital Experiences / Site.com) components from a source org on a newer Salesforce release to a destination org on an older release, the deployment fails with an unexpected error ID. This is Working as Designed (WAD) behavior — Salesforce does not allow importing Experience Cloud .site files from a newer release version to an older version.

Steps to Reproduce (Source Org: Summer '20 / Destination Org: Spring '20)

  1. In the source org, create a site via Setup > Customize > Digital Experiences > All Sites > New Site.
  2. Create an Outbound Change Set via Setup > Deploy > Outbound Change Sets > New.
  3. Click Add under "Change Set Components."
  4. Select Site.com and add the site from Step 1.
  5. Select Network and add the site from Step 1.
  6. Click View/Add Dependencies and add "All" Dependencies, then click Upload.
  7. Navigate to the destination org and go to Inbound Change Sets via Setup > Deploy > Inbound Change Sets. Click on the change set created in Steps 2–6.
  8. Click Validate/Default Apex Tests.
  9. The change set fails with an unexpected error ID (see above).
     
API NameTypeLineColumnError Message
Summer181Site.com00An unexpected error occurred. Please include this ErrorId if you contact support: 1671074043-21865 (-1999206631)


Note: Common error IDs associated with this version mismatch issue include: -1227793113, -1999206631, 993984830, -1154657483. The underlying error message is: "Cannot import data from a newer release."

Solución

Root Cause

This error occurs because Salesforce does not support importing Digital Experience (Site.com) components from a higher release version to a lower release version. The error is Working as Designed (WAD).

Resolution Options

  • Deploy or validate the change set in another environment that is on the same Salesforce release version (for example, another Summer '20 org, based on the steps above).
  • Wait until the target org is upgraded to the same release as the source org, then validate or deploy.

Update (September 2018)

Salesforce engineering addressed the misleading error ID behavior. Instead of an opaque error ID, Salesforce now displays a meaningful message clearly indicating a version mismatch. Note: This is still Working as Designed behavior — you cannot migrate Experience Cloud (Site.com) changes from a higher release version to a lower release version.

See also:
Error 'Mismatching Versions' when you install an app or deploy a change set
 

Número del artículo de conocimiento

000384918

 
Cargando
Salesforce Help | Article