# Is Replica Of Anomaly Reporting

Source: https://userguide.qualytics.io/data-quality-checks/is-replica-of/deep-dive/anomaly-reporting/

> **Warning: Deprecated: use Data Diff instead**
>
> The Is Replica Of rule is no longer maintained. [Data Diff](https://userguide.qualytics.io/data-quality-checks/data-diff/introduction/) replaces it with the same row-by-row comparison plus change-type filtering. This page is kept as a reference for checks that already exist; new checks should use Data Diff. Saving a check with the Is Replica Of rule, from the form or through the API, stores it as a **Data Diff** check.

How the Is Replica Of check reports a divergence, and where to find the differing rows.

## Anomaly Messages

Is Replica Of emits a **Shape Anomaly only**, one per failed comparison. The message counts the rows that differ and names both containers with their datastores in parentheses:

```text
N records differ between <container> (<datastore>) and <reference> (<reference datastore>)
```

When the comparison cannot get that far, the message says why instead: that the two containers hold different numbers of records, that one side is empty, that a compared field is missing on one side, or that a compared field is stored as a different type. See [Data Diff Anomaly Reporting](https://userguide.qualytics.io/data-quality-checks/data-diff/deep-dive/anomaly-reporting/) for the full set, which the two rules share.

The count has no singular form: one differing row still reads `1 records differ`.

When a filter is set, the Shape Anomaly message names it at the end of its first sentence, as `(applied to records where <expression>)`. Only the target's filter appears there; a filter set on the reference alone is not named. The exception is the message for two containers holding different numbers of records: when either side carries a filter, that message adds a sentence naming each filter against the container it applied to, ending in `only` when just one side is filtered. There is no per-row variant: the divergence belongs to the dataset, not to a single row.

## What the Numbers Mean

- **Differing rows:** the rows the comparison could not match, available in the anomaly's source records.
- **Row Identifiers:** when configured, they are what pairs a target row with its reference row and make the per-row detail readable.

## Source Records Behavior

With Row Identifiers configured, the per-row detail is rendered in the Comparison Source Records view, showing each differing row side by side. See [Comparison Source Records](https://userguide.qualytics.io/anomalies/deep-dive/anomaly-details/source-record/#comparison-source-records).

## Custom Anomaly Description

**Custom Anomaly Description** does not apply to this rule. The option replaces the message on Record Anomalies, and Is Replica Of emits a Shape Anomaly only.

## See Also

- **How It Works**

  The complete reference: definition, field scope, Row Identifiers, Comparators, filter behavior, and why coverage does not apply.

  [How It Works](https://userguide.qualytics.io/data-quality-checks/is-replica-of/deep-dive/how-it-works/)
- **Examples**

  A production scenario showing a replica that drifted from its source.

  [Examples](https://userguide.qualytics.io/data-quality-checks/is-replica-of/deep-dive/examples/)
- **Best Practices**

  Why to migrate to Data Diff, and how to keep an existing check useful until you do.

  [Best Practices](https://userguide.qualytics.io/data-quality-checks/is-replica-of/deep-dive/best-practices/)
- **Permissions**

  The team permission each action needs: view, create, edit, archive, restore, and delete.

  [Permissions](https://userguide.qualytics.io/data-quality-checks/is-replica-of/deep-dive/permissions/)

*Last updated: October 21, 2026.*
