You are here:
Version Mismatch Errors in Data Cloud One Orgs
Data Cloud One supports mixed versions between home and companion orgs, but version mismatches can cause temporary metadata syncing delays in some circumstances. Metadata syncing between a home org and its companion org can be delayed an object's schema changes between minor Salesforce versions. You can continue using all previously synced metadata even when syncing is in a temporary error state. Version mismatch errors resolve themselves as soon as both orgs upgrade to the same version.
Version mismatches between Data Cloud One home and companion orgs can happen during minor upgrades, which happen as often as every two weeks. Although updates during major releases are typically backwards-compatible, some minor versions introduce schema changes that aren’t. New Salesforce versions roll out to different data centers at different times over a period of 24 to 72 hours. If your home org and companion org are provisioned at different data centers, especially if they’re in different regions, their versions can mismatch during the rollout period.
Impacts of Version Mismatches
- You can establish new companion connections, but your initial metadata sync could show a pending or error status until your home org and companion org versions match.
- Syncing pauses if a version mismatch causes an object's schema to be different between the two orgs and if that particular object is being used. For example, if a Salesforce release introduces a new property in a data model object (DMO) and you are using that DMO, new metadata won’t sync until the home and companion orgs are on the same version.
- All previously synced Data 360 metadata remains usable in the mismatched companion org. However, new or changed metadata isn’t available until syncing resumes.
Checking for Version Mismatches
We recommend checking what release version each org in your Data Cloud One org cluster is using before establishing new companion connections or if you notice delays in metadata syncing. You can’t change the timing of Salesforce updates, but knowing the current versions of each org helps you plan ahead.
To check versions, log into each Salesforce org. Append /releaseVersion.jsp to
your domain URL. For example,
https://yourdomain.lightning.force.com/releaseVersion.jsp. The page
displays ReleaseName=[Your Precise Version]. For example,
ReleaseName=[111.22.33].
Compare the version for both the home and companion orgs. An org's minor version number is
indicated by the second set of numbers. For example, if the version number is
111.22.33, the number 22 indicates the minor version. Metadata
syncing errors are usually caused by minor version mismatches.
Handle Version Matches
You don’t need to take any action to resolve version mismatches. Version mismatches resolve within 24 to 72 hours. Metadata syncing automatically resumes when your home org and companion org versions match and schema mismatches resolve.
