Skip to content

Is Address Troubleshooting

Common problems when creating and running an Is Address 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.

Addresses From One Country Are All Flagged

Every row from a given country is reported.

Cause: One of the Required Labels does not exist in that country's address convention, such as requiring a state where none is used.

Resolution: Scope the check with a filter on the country, or drop that part from the required list and cover it with a country-specific check.

A Complete-Looking Address Is Flagged

An address that reads correctly is reported as missing a part.

Cause: The parsing could not recognize that part in the value, usually because the format is unconventional, abbreviated, or missing separators.

Resolution: Normalize the column upstream so the parts are separated consistently, or relax the required list when the format is legitimate for your data.

Rows With NULL Values Are Not Flagged

Rows with an empty address pass the check.

Cause: This is by design: NULL values pass. An empty string, however, is a present value with no parts and is reported.

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

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.