Skip to content

Volumetric Troubleshooting

Common problems when creating and running a Volumetric 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 configuration is incomplete or inconsistent. The most common reasons are that neither Min Value nor Max Value is filled in, or that Min is greater than Max.

Resolution:

  1. Review the error message: it explains what needs attention.
  2. Fill in at least one limit, and make sure Min is not greater than Max. For Percentage Change, enter the limits in percent.

Validation checks the configuration without counting the container's rows, so a successful validation does not confirm that the container can be measured or that its history is complete. The first Scan does.

The Row Count Went Out of Range but No Anomaly Was Created

The Observability chart shows a day outside the limits, but the Anomalies list has nothing for the check.

Cause: No Scan evaluated the check on that day. Observability measurements update the chart every day, but only a Scan asserts a Volumetric check and creates anomalies. A Scan that does not include the Metadata category skips the check as well.

Resolution: Schedule a Scan on the container with the Metadata category selected, timed after the load you expect. See Select Check Categories and Schedule Options.

The Check Is Never Asserted

Every Scan records the check as Not Asserted, with a message that there were insufficient historical volume measurements.

Cause: The comparison needs a daily count for each of the previous days in its Measurement Period, and at least one of those days has none. This is common on containers without Volume Tracking, where counts come only from Scans and Profiles and any day without one leaves a gap, and right after a check is created with a long Measurement Period.

Resolution:

  1. Turn on Volume Tracking in the container's Observability Settings, so a count is recorded every day.
  2. Wait until the history covers the whole Measurement Period: N days for a change comparison, N - 1 days for Absolute Value.

See The History the Check Needs.

The Check Was Not Asserted Because the Volume Could Not Be Measured

The Scan records the check as Not Asserted, with a message that the current volume could not be measured.

Cause: The Scan could not read the container's row count, usually because of a connection or permission problem on the source.

Resolution: Review the message for the underlying reason and fix access to the container. If the container is marked as Unloadable, follow the steps in Unloadable Container Error.

Saving a New Comparison Fails

Changing the Comparison and clicking Update returns an error saying the check has already been asserted.

Cause: The comparison is locked once a Scan has included the check, because the history it was evaluated against would no longer mean the same thing.

Resolution: Create a new Volumetric check with the comparison you want, then archive the old one. The Measurement Period and the limits of the existing check can still be changed.

Saving or Activating Fails Because Another Check Conflicts

Clicking Save, Update, or Activate returns an error saying an existing check conflicts.

Cause: The container already has an Active Volumetric check with the same comparison and Measurement Period. Only one is allowed per combination, whatever its limits, and AI Managed checks count.

Resolution: Open the check the message names. Edit it instead of creating a second one, or give the new check another comparison or Measurement Period. See One Active Check per Comparison and Period.

The Check Alerts on Every Weekend or Holiday

A 1 day change check fires every Saturday and Monday because traffic drops and recovers.

Cause: A one-day comparison treats a weekly pattern as a sudden change.

Resolution: Use a Measurement Period of 7 days, so each day is compared with the same weekday a week earlier, or widen the limits of the daily check. See Best Practices.

An AI Managed Check Stopped Adjusting

The limits of a check that used to follow the data no longer change.

Cause: Someone changed its comparison, Measurement Period, or limits, which converted it to Authored. Authored checks keep the limits set on them.

Resolution: Keep the Authored check if its limits are intentional. Otherwise, archive it so it stops raising anomalies. See AI Managed Volumetric Checks.