Aglet

Triage Cumulative Report Reset Boundaries

Cumulative triage asks which rows belong in a running total and when that total starts again. Inspect period ordering, group keys, missing periods, filters, and reset labels in a compact fixture. Preserve two groups and a reset edge so a smooth line cannot hide a carryover that changes the report question.

Establish what is happening

  1. State the accumulation rule

    Write the measure, ordering field, group or partition key, start point, reset event, and treatment of missing periods. Record whether the value is a running sum, maximum, balance, or other accumulated state. Keep expected values beside each ordered row.

  2. Trace the running value

    Follow filtered rows through ordering, grouping, window or iterative calculation, reset detection, formatting, and chart or table display. Compare the value before and after each boundary. Mark the first stage that carries a value across groups or restarts without a visible rule.

  3. Bound affected outputs

    List charts, cards, tables, exports, filters, and period comparisons using the cumulative measure. Separate calendar-to-date, group-to-date, and lifetime views. Ask the metric owner to settle whether a missing period carries forward, breaks the series, or contributes no value.

What to carry forward

Triage is complete when accumulation key, reset rule, first carryover or restart, affected outputs, and owners are recorded. Keep the result provisional when the report shows a running value but does not state its start or reset boundary.

Technical background: Metabase documentation.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow