# Is Replica Of Check FAQ

Source: https://userguide.qualytics.io/data-quality-checks/is-replica-of/faq/

> **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.

Answers to common questions about the deprecation, the migration to Data Diff, and how anomalies are reported, grouped by topic.

## Deprecation

### Is Is Replica Of still supported?

Existing checks keep running, but the rule is no longer maintained and should not be used for new checks. [Data Diff](https://userguide.qualytics.io/data-quality-checks/data-diff/introduction/) is its replacement.

### What does Data Diff add?

**Diff Change Types**, which restricts anomalies to a chosen subset of `added`, `removed`, and `changed`. Everything else, including Row Identifiers, Passthrough Fields, and the Comparators, works the same way.

### How do I migrate?

Create a [Data Diff](https://userguide.qualytics.io/data-quality-checks/data-diff/how-tos/create-a-check/) check with the same fields, Row Identifiers, Passthrough Fields, reference container, and Comparators, confirm it reports what you expect, then archive the Is Replica Of check.

### Will my existing checks stop working?

No. They continue to evaluate. They simply will not receive new capabilities, and the guidance is to replace them.

---

## Behavior

### Why is there no Coverage setting?

The rule reports any difference the Comparators do not tolerate, so there is no per-row violation rate to threshold. The `coverage` field on the API payload accepts only `null` or `1`; any other value is rejected with `422`.

### What happens without Row Identifiers?

The two sides are compared as sets, so the check can only report that they differ. With identifiers, each target row is paired with its reference row and the per-row detail becomes readable.

### How are NULLs compared?

A value that is `NULL` on both sides matches. A value present on one side and `NULL` on the other counts as a difference.

---

## Anomaly Reporting

### What does the anomaly report?

A single Shape Anomaly reading `N records differ between <container> (<datastore>) and <reference> (<reference datastore>)`. When the comparison cannot run row by row, the message says why instead: that the row counts differ, that one side is empty, that a compared field is missing, 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.

### Does Is Replica Of produce Record Anomalies?

No. The rule is Shape-only; the divergence belongs to the dataset.

### Where do I see the differing rows?

In the anomaly's Comparison Source Records view, provided Row Identifiers are configured.

### What permission do I need to create or edit an Is Replica Of check?

The **Drafter** team permission on the datastore covers Draft work (creating a check as Draft or editing it while it stays Draft). Anything that puts the check into evaluation, such as creating or editing an Active check, archiving, or deleting, requires the **Author** team permission (or above). Viewing only requires **Reporter**. See [Permissions](https://userguide.qualytics.io/data-quality-checks/is-replica-of/deep-dive/permissions/) for the full matrix.

**Still have questions?**
Contact the Qualytics support team at
[support@qualytics.ai](mailto:support@qualytics.ai).

*Last updated: October 16, 2026.*
