# Max Value Check FAQ

Source: https://userguide.qualytics.io/data-quality-checks/max-value/faq/

Answers to common questions about how the Max Value check caps a numeric field, how the ceiling behaves, and how anomalies are reported, grouped by topic.

## Behavior

### Is the ceiling inclusive or exclusive?

Inclusive. The comparison is `value <= maximum`, so a row holding exactly the maximum passes. Max Value has no inclusivity toggle; use [Less Than](https://userguide.qualytics.io/data-quality-checks/less-than/introduction/) when the limit itself must be rejected.

### Why is Min Value exclusive while Max Value is inclusive?

They are asymmetric by design: Max Value accepts the ceiling (`value <= maximum`), while [Min Value](https://userguide.qualytics.io/data-quality-checks/min-value/introduction/) requires values strictly above the floor (`value > minimum`). Keep that in mind when the two are used as a pair; [Between](https://userguide.qualytics.io/data-quality-checks/between/introduction/) avoids the ambiguity by letting you set inclusivity on each side.

### What happens on a numeric field nested inside an array?

It cannot be checked with Max Value. The rule accepts `Integral` and `Fractional` fields only, and has no array-element mode. A numeric field nested inside an array of structs is stored as an array, so it is excluded too. To check the numbers inside an array element by element, use [Between](https://userguide.qualytics.io/data-quality-checks/between/introduction/), [Not Negative](https://userguide.qualytics.io/data-quality-checks/not-negative/introduction/), or [Positive](https://userguide.qualytics.io/data-quality-checks/positive/introduction/), which support array elements.

### How are NULL values treated?

NULLs **pass**. A row with `NULL` in the evaluated field is not counted as a violation. Max Value only asserts that present values satisfy the rule. If the field must also be populated, pair the check with a [Not Null](https://userguide.qualytics.io/data-quality-checks/not-null/introduction/) check on the same field.

### Which field types can I check?

Numeric fields only: integers and decimals. An array column is rejected with `422`, and so is a numeric field nested inside an array of structs, since it is stored as an array. A number stored as text does not appear in the field picker; expose it with a numeric type first.

### Does the filter run before or after the comparison?

Before. The platform applies the filter first and then evaluates the comparison only on the rows that pass the filter. Filtered-out rows cannot trigger an anomaly and are not counted in the totals.

---

## Anomaly Reporting

### What do the anomaly messages look like?

**Record Anomaly:** `<field> has the value <value>, which is above the maximum of <limit>`

**Shape Anomaly:** `<field> values are above the maximum of <limit>, 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.

### Does Max Value produce Record Anomalies, Shape Anomalies, or both?

On a scalar numeric field at 100% coverage (the default), violating rows are reported as Record Anomalies. Below 100% coverage, a failed coverage assertion produces one Shape Anomaly for the dataset.

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](https://userguide.qualytics.io/operations/scan/deep-dive/scan-settings/#maximum-record-anomalies-per-check).

### Does Custom Anomaly Description work for Max Value?

Yes. Max Value emits Record Anomalies, so the `anomaly_message_field` payload field (and the **Custom Anomaly Description** toggle in the UI) applies.

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.

---

## Configuration

### Can I lower the coverage on a Max Value check?

Yes. Coverage at `1.0` (100%) means every row must pass. Lowering coverage to `0.995` allows up to 0.5% of rows to fail without raising an anomaly; once the failing fraction goes past that, the check reports a Shape Anomaly. Use lower coverage with care: a real regression that happens to fall just under the threshold will not raise an alert at all.

### Can I move the ceiling on an existing check?

Yes. In the UI, open the check, change **Value**, and click **Update**; see [Edit a Check](https://userguide.qualytics.io/data-quality-checks/max-value/how-tos/edit-a-check/) for the full steps. Through the API, a `PUT` to `/api/quality-checks/{id}` updates `properties.value`. The rule type, the target container, and the associated Check Template stay immutable; see the [API page](https://userguide.qualytics.io/data-quality-checks/max-value/api/) for the editable/immutable matrix.

### What permission do I need to create or edit a Max Value 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/max-value/deep-dive/permissions/) for the full matrix.

### Should I use Max Value or Between?

Use Max Value when only the upper limit is a real rule. When the value also has a meaningful floor, [Between](https://userguide.qualytics.io/data-quality-checks/between/introduction/) states both sides in one check and lets you choose inclusivity per side.

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

*Last updated: October 19, 2026.*
