Skip to main content

Overview

Diff answers one question: what’s actually different between these two pipelines right now? Diff is completely read-only. Nothing is written and nothing is published. What you see in a Diff is what a sync would act on.
Required permissions
  • Data Pipelines: Access
  • Manage Production Pipelines or Manage Dev Pipelines: Read on both pipelines you compare
The target picker lists only pipelines you can read; opening a Diff against a pipeline you can’t read shows it as not found. The main pipeline is always governed by Manage Production Pipelines. See roles and permissions.

Comparing Two Pipelines

1

Open the Actions Menu

From the pipelines list, click the three-dot menu (⋮) on the pipeline you want to compare from and hover Manage.
2

Select Diff

Click Diff to open the comparison dialog.
3

Pick the Target

Choose the pipeline to compare against.
4

View the Diff

Click View Diff. You step through every differing entity. There are no toggles and no commit button.Entities that are identical on both sides are skipped, so everything you see is a real difference.

When to Use Diff

  • Before deciding whether to sync at all. If nothing differs, there’s nothing to sync.
  • Before syncing into production. A sync deletes target-only mappings and metrics. A Diff shows you which mappings exist only in the target, so you can review them before you commit; it doesn’t preview metric deletions.
  • To hand a colleague a review. Walk the Diff together before a large sync.
  • To confirm a sync landed. Diff the two pipelines afterward — a clean comparison means the target’s mappings match the source’s. Diff doesn’t compare metrics; check the Sync Result for those.
  • To measure drift. Diff a long-lived test pipeline against main to see how far it has diverged before starting new work.

Reading a Diff

Each differing entity shows a one-line summary of what differs — a count such as 3 traits, 1 join, or only in source / only in target for an entity that exists on just one side. Entities that depend on other entities list those as depends on chips. Differences are grouped by the part of the entity they belong to — the entity itself, or one of its maps — and tagged Add, Update, Remove, or Unchanged, from the perspective of applying the source to the target.
“Remove” Means Target-OnlyA row tagged Remove exists in the target and not in the source. A sync would delete it. Diff itself never removes anything.
A Rename Reads as a Remove Plus an AddComparisons match items by their stable key, so something renamed on one side appears as one item removed and a different one added. If a Diff looks larger than you expected, check for renames before concluding something went wrong.

Troubleshooting

The Diff Shows More Differences Than Expected

Problem: You changed three fields but the Diff lists many more. Solution:
  • Check for renames — they appear as a removal plus an addition.
  • Check whether the target has changed independently since you last looked. A Diff compares both sides as they are right now, not just your work.
  • Confirm you’re comparing against the pipeline you intended.

Diff Is Missing from the Menu

Problem: The three-dot menu doesn’t offer Diff. Solution:
  • Verify your role has Read on at least two pipelines. Diff needs a second pipeline to compare against.
  • On an access-controlled entity, verify your role has Manage Access Control Entity Rules Update. Without it the entity row menu doesn’t appear.

Syncing a Single Entity

Apply what the Diff showed you, one entity at a time

Syncing Pipelines

Apply it across the whole pipeline

Sync Overview

What a sync adds, updates, and deletes