Keep the lesson for the next incident
Retain calendar exemplars
Keep closed, open, equal-length, unequal-weekday, missing-day, and boundary-date fixtures with expected deltas and labels. Record calendar basis, timezone or reporting zone, refresh time, and source revision. Preserve the original unlabeled comparison beside the corrected context.
Classify recurrence signals
Review earlier questions for date predicates, refresh timing, incomplete status, weekday shape, future rows, and exports that dropped period context. Group named examples by missing definition or review cue. Avoid treating every changing current value as a defect.
Assign comparison stewardship
Make the report owner maintain the alignment statement and the metric owner approve its meaning. Add a trigger when calendar policy, refresh timing, or comparison copy changes. State which partial cases the fixtures detect and which business decisions still require human judgment.
What to carry forward
The learning record is complete when it links the false trend to a missing period definition or completeness cue, preserves calendar fixtures, and names an owner and trigger. Keep intentional to-date monitoring labeled so future readers do not reopen it as an accidental comparison.
Technical background: Google Cloud 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