Skip to content

Between Troubleshooting

Common problems when creating and running a Between 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.

A Value Sitting Exactly on a Boundary Is Flagged

Rows whose value equals Min or Max appear as anomalies.

Cause: That side of the range is exclusive. The anomaly message shows the boundaries but not their inclusivity, so an exclusive boundary looks like a false positive at first glance.

Resolution: Open the check and turn on the Inclusive toggle for that side. When several checks partition a scale, prefer keeping the lower bound inclusive and the upper bound exclusive so no value belongs to two ranges.

Rows With NULL Values Are Not Flagged

Rows with an empty field pass the check.

Cause: This is by design: NULL values pass. Between only constrains present values.

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

The Field Does Not Appear in the Field Picker

The column you want to check is not listed under Field.

Cause: The picker only lists numeric fields (and arrays of numbers). A number stored as text is excluded.

Resolution: Expose the column with a numeric type upstream, or project it through a Computed Field, then select that field.

An Array Row Fails Although Most Elements Are in Range

A row with an array field is flagged even though only one element is out of range.

Cause: On array fields the check evaluates every element, and the row fails as soon as one element falls outside the range.

Resolution: This is expected behavior. Review the flagged row's array to find the offending element.

Only One Boundary Is a Real Rule

The check works but one of the boundaries had to be invented.

Cause: Between always evaluates both sides, so a single-sided rule forces an artificial second boundary that may start firing when the data legitimately grows.

Resolution: Use Min Value or Max Value for a single-sided rule, or Positive and Not Negative for the common floors.

An Edited Check Keeps Behaving the Old Way

You moved a boundary 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 the ones the updated range now accepts. See What Happens to Existing Anomalies.

No Anomalies Although Values Are Out of Range

A Scan ran, the column clearly holds out-of-range values, but nothing was reported.

Cause: One of three 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, test the filter expression against the offending rows, and 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.