Overview
A successful whole-pipeline sync makes a target pipeline match a source pipeline in a single operation: every entity’s mapping configuration, plus all of its metrics. Because related entities move together, relationships stay consistent — which is why this is the recommended default over syncing entities one at a time. If the metrics fail to copy, the mapping changes still go through; see The Metrics Were Not Copied.Nothing in the source pipeline changes. A sync only writes to the target.
Required permissions
- Data Pipelines: Access
- Sync: Update on the source pipeline (Manage Production Pipelines or Manage Dev Pipelines) and Manage Silver Entities Update
- Sync from main: Manage Production Pipelines Read and Manage Silver Entities Update, plus Update on the target pipeline
Syncing a Pipeline
1
Open the Sync Dialog
From the pipelines list, click the three-dot menu (⋮) on the pipeline you’re syncing from, hover Manage, and click Sync.A dialog opens, titled Sync
{source} to {target}.2
Check the Direction
A blue panel labeled Syncing shows From (the pipeline you clicked) and To (the target).Read this before anything else — it’s the fastest way to catch a backwards sync.
3
Pick the Target
The Target pipeline dropdown defaults to your main pipeline, shown as
{name} (main). Change it if you’re syncing somewhere else.The source pipeline is never offered as its own target.4
Read the Warning
A pipeline sync always overwrites the target — there is no strategy to choose. The dialog says so:If you’re unsure what the target contains, run a Diff first.
5
Write a Reason
The Reason for Sync box is required — the Sync button stays disabled until you fill it in.Your reason is saved to the target’s change history, so write something a colleague would understand in three months:
“Syncing new billing-attorney fields validated on test.”
6
Decide About Publishing
The Publish the target pipeline after syncing checkbox is off by default. Until the target is published, it keeps running the mappings it had before the sync.This is the step people miss — see Publishing After a Sync.
7
Click Sync
Click Sync to apply.A full-screen overlay reads
Syncing "{source}" to "{target}"... while it runs.8
Read the Result
When it finishes you’ll get a notification summarizing the outcome, for example:If anything needs your attention — metric changes, a skipped entity, a failed publish, a failed metric copy, or nothing having changed — a Sync Result window also opens.
Sync from Main
⋮ → Manage → Sync from main needs Manage Production Pipelines Read and Manage Silver Entities Update. It opens the same dialog with the direction already reversed: main is the source, and the pipeline whose menu you opened is already selected as the target. Everything else works identically. This is the “reset my test pipeline to match production” shortcut.Reading the Results
Every sync reports an outcome for each entity and each metric change. A notification always appears; the Sync Result window opens on top of it when something is worth a closer look. The window shows counts for entities and metrics, then one table with four columns — Name, Type, Outcome, and Details. Type tells entities apart by layer (for example, Silver) and metrics by kind (for example, Atom).
Metrics are copied after the mappings, so if the metric copy fails, the window says The mappings were synced, but the metrics were not copied — your mapping changes are kept, and running the sync again retries the metrics.
If you asked to publish, a banner reports how that went separately from the sync itself — green (“Published
{target} — it now runs the synced mappings.”) or red, with the failing entities listed.
Where to Look Later
Every entity a sync changed gets an entry in the target’s change history, stamped with your reason, your user, and the time. That history is a full snapshot of the entity, so a sync is reviewable — and revertible — after the fact. This is why the reason field is required.Best Practices
Troubleshooting
The Sync Button Is Disabled
Problem: You’ve selected a target but Sync stays greyed out. Solution:- Fill in the Reason for Sync field — it’s required.
- Confirm a target pipeline is selected in the dropdown. The target list shows only pipelines you can update.
- Verify your role has Manage Silver Entities Update in addition to Update on the pipeline.
Nothing Changed
Problem: The result lists every entity and metric as Unchanged. Solution:- The two pipelines already match. Run a Diff to confirm.
- Confirm you saved your work on the source pipeline before syncing.
The Metrics Were Not Copied
Problem: The Sync Result window says the mappings were synced but the metrics were not copied. Solution:- Read the error shown under the message.
- Confirm you have permission to edit metrics on the target pipeline.
- Otherwise, run the sync again to retry. Your mapping changes are already in place, but if you asked to publish, publishing was skipped; the retry publishes once the metrics copy.
The Target Lost All Its Metrics
Problem: After a sync, the target pipeline has no metrics. Solution: The source pipeline had none. A sync makes the target’s metrics match the source’s, so syncing from a pipeline with no metrics deletes every metric in the target. Recreate them on the source and sync again.The Target Still Runs the Old Mappings
Problem: The sync succeeded but reports and scheduled runs still reflect the old configuration. Solution: The target hasn’t been published. See Publishing After a Sync.No Manage Submenu
Problem: The pipeline’s three-dot menu doesn’t show Manage. Solution: The main pipeline has no Manage submenu by design. To sync into main, start from the pipeline you’re syncing from. If Sync or Sync from main is missing on another pipeline, check the permissions listed at the top of this page.Related Topics
Syncing a Single Entity
Move just one entity instead
Comparing Pipelines
See exactly what a sync would change
Sync Overview
Scopes, limits, and publishing
