You are here:
Resolve Metadata Drift in Data Cloud One Sandboxes
Resolve metadata drift and synchronization errors when connecting a Data Cloud One companion sandbox to a home sandbox.
Required Editions
| Available in: All Editions supported by Data 360. See Data 360 edition availability. |
| User Permission Set Needed | |
|---|---|
| View and delete drifted components in the companion sandbox: | Data Cloud One User AND access to the components to be deleted |
When connecting a companion sandbox to a home sandbox, the connection can fail to complete and the Companion Sync Status shows or changes to Error. This error indicates metadata drift between the sandboxes.
Metadata drift occurs when inherited Data 360 metadata in the companion sandbox diverges from metadata definitions recognized by the home sandbox. Common causes include:
- The home and companion sandboxes were created or refreshed at different times, and production metadata changed in the interim.
- Shared metadata or data spaces that the companion sandbox expects were deleted from the home sandbox before the connection was established.
- Metadata definitions were modified in the home sandbox and conflict with inherited companion sandbox configurations.
When drift occurs, delete only the drifted entities identified in the companion sandbox error log. A full metadata cleanup isn’t required.
- In the companion sandbox, from Setup, enter Data Cloud in the Quick Find box, and then select Data Cloud Connection Details.
- Locate the companion connection displaying an Error status and navigate to the companion connection details page.
-
Next to the error status, click the Download icon to retrieve
the error log.
Error logs are available for download only from the companion sandbox. While the home sandbox displays the error status, it doesn't provide the log file.
- Open the error log and review the specific companion entities causing the drift.
- If you can’t access the Data Cloud One app, navigate to Data Cloud Connections in Setup, click Assign Users, and assign the Data Cloud One User permission set to your user account.
- From the App Launcher, find and select Data Cloud One app.
- Navigate to the tabs corresponding to the entities in the error log, and delete the conflicting items.
Delete entities in reverse dependency order. Remove downstream dependent assets, such as Flows, Agentforce actions, or enrichments, first, and then delete parent entities, such as Calculated Insights or Segments.
Data Cloud One automatically detects the cleanup during the next sync cycle and completes the connection. You shouldn’t re-initiate the connection.
Resolve Drift Caused by Deleted Data Spaces
If a shared data space is deleted from the home sandbox before connecting a companion sandbox that inherited it, the connection fails. To establish the connection, take one of these actions:
- Connect the companion sandbox to a compatible home sandbox that contains the original data space.
- Refresh the appropriate sandboxes to align their metadata lineages.
