Not Future Anomaly Reporting

How the Not Future check reports violations: the anomaly messages it produces, what the numbers mean, how the offending value appears in Source Records, and how to replace the default message with a value from your own data.

Anomaly Messages

On a Date or Timestamp field at 100% coverage, Not Future reports violating rows as Record Anomalies. Below 100% coverage, a failed coverage assertion produces one Shape Anomaly for the dataset. On an array field the rule is evaluated element-wise as a field-level check, which always reports a Shape Anomaly. The two templates are:

Record Anomaly

<field> has the value <value>, which is dated in the future

Shape Anomaly

<field> values are dated in the future, affecting N of M asserted records

When a filter is set, the message names it at the end of its first sentence, as (applied to records where <expression>). Record and Shape Anomaly messages both carry it.

Scan settings can group a large number of Record Anomalies into one rolled-up Shape Anomaly, which carries the Shape Anomaly message. This behavior applies across rule types and is documented under Maximum Record Anomalies per Check.

What the Numbers Mean

• N: the number of rows with a future date.
• M: the total number of rows the check evaluated (after the filter, if any). Rows with NULL values count in this total because they pass.

For a Shape Anomaly, the failing share appears in the opening line of the anomaly's description, for example 2 of 4 records (50%) in ACCOUNTS failed 1 check during full scan #4821. That line counts against every record the scan processed, so on a filtered check its denominator is no smaller than the check's own asserted count. See Anomaly Description.

Source Records Behavior

The offending cell is highlighted with an orange outline and an orange-tinted background in the Source Records view. Compare it against the Scan's run time, which is the boundary the value was measured against, rather than against the time you are reading the anomaly.

Custom Anomaly Description

Not Future supports Custom Anomaly Description because it emits Record Anomalies. The option is anomaly_message_field in the API and the Custom Anomaly Description toggle in the UI.

When the option points at another column on the same row, the Record Anomaly message becomes that column's value for the violating row, shown as written. When the column is null, missing, or empty, the message falls back to the rule's standard wording, and when the column is masked the message reads <masked>. Shape Anomaly messages are unaffected.

See Also