Skip to content

Time Distribution Size Anomaly Reporting

How the Time Distribution Size check reports violations: the Shape Anomaly it produces, what the percentage counts, and why the anomaly is about segments rather than rows.

Anomaly Messages

Time Distribution Size reports a Shape Anomaly, never a Record Anomaly. The rule evaluates the count of a time segment, so no individual row is at fault.

Shape Anomaly

For the field '<field_name>', X.XXX% of the <interval> time segments have record counts outside the range of <min_count> to <max_count>

Reading the message:

  • X.XXX% is the share of time segments that fell outside the range, not the share of records. A table with 30 daily segments where 3 are out of range reports 10.000%, whatever the row counts involved.
  • <interval> is the interval configured on the check: Yearly, Monthly, Weekly, Daily, or Hourly.
  • <min_count> and <max_count> are the two bounds, both inclusive.

The anomaly carries the segments that failed, so you can see which periods are short and which are oversized rather than only that something is off. A short segment and an oversized one produce the same message, and telling them apart is the first thing to look at: short usually means a load that stopped early, oversized usually means one that ran twice.

When a filter is set, the message ends with [filter: <expression>] so the evaluated scope is visible in the alert.

Because the anomaly belongs to the distribution rather than to a set of rows, the Source Records view has nothing to list.

Custom Anomaly Description does not apply to this rule. The option replaces the message on Record Anomalies, and Time Distribution Size emits a Shape Anomaly only.

See Also

  • Examples

    Three production scenarios with sample data, the resulting anomaly message, and the SQL equivalent of what the check evaluates.

    Examples

  • Best Practices

    Guidelines for picking the interval, sizing the range, and handling seasonality.

    Best Practices

  • Permissions

    The team permission each action needs: view, create, edit, archive, restore, and delete.

    Permissions

  • How It Works

    The complete reference: definition, field scope, the interval, the count range, what a segment is, filter behavior, and why coverage does not apply.

    How It Works