Entry Points and Resuming

The Recipes page is not the only way into the Data Reconciliation recipe. An active Data Diff check opens the recipe at Scan, and a Data Diff anomaly opens it at Reconcile with its mismatches loaded. This page covers those two entry points and how the recipe keeps your progress between visits.

Entry Points

Both buttons live on the datastore page, on the details of a check or an anomaly. Each appears only for the Data Diff rule type and only when you hold the permissions the recipe needs there. Entering the recipe this way replaces any progress you had in it, since the recipe now works on the check or anomaly you opened.

Scan in Recipe

Scan in Recipe is a button on the details of an Active Data Diff check. It loads the check's two assets, identifiers, compare fields, and tolerances, and opens the Scan step directly, skipping the build phase because the check is already validated. The scan does not start on its own; you click Scan when ready. This is the way to rerun the recipe after new loads on either side, since the check is still active. See Scan a Check in the Recipe.

Reconcile in Recipe

Reconcile in Recipe is a button on the details of an anomaly raised by a Data Diff check, as long as the anomaly is not archived. It loads the check behind the anomaly and the anomaly's mismatched rows, and opens the Reconcile step with them ready to resolve. This is how a scan run outside the recipe, whether by hand, on a schedule, or from a Flow, hands its mismatches back to the recipe. See Reconcile an Anomaly in the Recipe.

Entry point	Where	Shown for	Opens at	Preloaded
Scan in Recipe	Check details	Active Data Diff checks	Scan	The check's configuration
Reconcile in Recipe	Anomaly details	Anomalies of a Data Diff check, not archived	Reconcile	The check's configuration and the anomaly's mismatched rows

Unlike Entity Resolution, a Data Diff check that is not active yet has no Open in Recipe option. Build the check in the recipe, or activate it on the datastore page and use Scan in Recipe.

Resuming

The recipe keeps your progress as you work: the step you are on, both assets, the identifiers, fields, tolerances, the check it created, the scan results, and your resolutions. When you leave and come back, the Recipes page shows the Data Reconciliation card with an In progress pill and a Continue button, and clicking it reopens the recipe where you left it.

Progress is kept in your browser session, per recipe, rather than as a record in Qualytics. That has two consequences:

A different browser, another computer, or a cleared session starts the recipe fresh. To pick up the same work there, enter through the check or the anomaly instead.
Everything the run produced persists regardless: the check, the scan, the anomaly, and the outputs in the enrichment destination are ordinary platform objects and stay where they are.

The mismatched rows loaded for reconciliation can be large, so they are cached separately in the browser and reloaded when you continue. If they are missing, the Reconcile step points you back to Scan to load them again.

Starting Over

Start over in the recipe header, and Start Over on the Complete step, clear your progress and return to the first step. The dialog spells out what that means:

This clears your progress and returns to the first step. Nothing the run already produced is deleted.

Recipe Progress: your answers are cleared and the recipe reopens at the first step.
Quality Check: any check the recipe created stays active on the asset.
Scans and Anomalies: scans already run and the anomalies they reported remain available.
Materialized Tables: tables already written to the enrichment datastore stay as they are.

Starting over is therefore safe at any point. See Resume or Start Over.