Skip to content

Exists In Troubleshooting

Common problems when creating and running an Exists In check, their causes, and how to resolve them.

Validation Fails When Creating the Check

Clicking Validate returns an error instead of a success message.

Cause: The rule could not run against the selected data. The most common reasons are an invalid Filter Clause expression, a connection problem with the source, or a container that failed to load.

Resolution:

  1. Review the error message: it explains what needs attention.
  2. Check the Filter Clause for typos: it must be a valid SQL WHERE expression for the selected container.
  3. If the message says the container is marked as Unloadable, the container was skipped after repeated operation failures. Follow the steps in Unloadable Container Error.

Values That Look Right Are Flagged

A target value appears identical to one in the reference.

Cause: The match is exact. A padded identifier, a different case, or trailing whitespace makes two visually identical values distinct.

Resolution: Normalize both sides upstream, or expose a Computed Field with the canonical form and point the check at it.

Every Row Fails

The check reports essentially the whole column.

Cause: Usually one of two things: the reference filter is so narrow that the lookup set is empty or tiny, or the two columns are not comparable (a number looked up against text).

Resolution: Run the reference filter against the reference container and confirm it returns the values you expect, then confirm both columns carry the same kind of value.

Rows With NULL Values Are Not Flagged

Rows with an empty target field pass the check.

Cause: This is by design: a NULL has no value to look up.

Resolution: Pair the check with Not Null on the same field to also require presence.

The Check Started Firing Without Anyone Editing It

Anomalies appear on a check that was green for months.

Cause: The lookup set is read at scan time. A reference container that lost rows, or a reference filter whose result changed, makes the same check stricter.

Resolution: Check the reference container first, before assuming the target data changed.

An Edited Check Keeps Behaving the Old Way

You changed the configuration but the anomaly list did not change.

Cause: Edits take effect on the next Scan. Saving the check does not re-evaluate the data, and anomalies raised under the previous configuration are not modified.

Resolution: Run a Scan on the container (or wait for the scheduled one). Old anomalies stay open until you triage them or a Full scan with Auto Resolve clears them. See What Happens to Existing Anomalies.

No Anomalies Although the Data Looks Wrong

A Scan ran, the data clearly breaks the rule, but nothing was reported.

Cause: One of these configurations is excluding the violations:

  • The check is in Draft status: Draft checks are not evaluated by Scans.
  • The Filter Clause excludes those rows before the evaluation runs.
  • Coverage is below 100% and the failing fraction stayed within the tolerance, so the check passed.

Resolution: Confirm the check is Active and test the filter expression against the offending rows. Then review the coverage setting; see Coverage and Tolerance.

Expected One Anomaly per Row, Got a Single Rolled-Up One

Many rows failed, but the scan reported one Shape Anomaly instead of per-row Record Anomalies.

Cause: When the number of failing rows exceeds the scan's rollup threshold, the per-row findings are grouped into one rolled-up Shape Anomaly.

Resolution: This is expected behavior; the rolled-up anomaly carries sampled source records. To change the threshold, see Maximum Record Anomalies per Check.