Establish what is happening
Bind the artifact to its run
Record the controlled schedule, generation time, selected report, filters, and intended data window. Compare those with the labels included in the artifact. Keep generation time separate from data freshness; a recently created snapshot can still contain results computed from an older source or cached report state.
Compare applied and visible context
Inspect the parameters used to generate the snapshot and the context its recipient can actually see. Identify missing filters, period labels, units, or update timestamps. A correct scheduled definition does not make the artifact self-explanatory when those selections are omitted from the exported image, table, or attached document.
Reconstruct an equivalent interactive view
Open the report with the same controlled parameters and relevant data state where available. Compare values and context with the artifact, keeping later data changes explicit. If the snapshot cannot be tied to a specific run or parameter set, record that evidence gap instead of assuming a mismatch proves incorrect calculation.
What to carry forward
End with the schedule and run identity, applied parameters, data freshness, and context missing from the artifact. State whether an equivalent comparison was possible. The next owner should be able to distinguish stale data, changed defaults, and omitted snapshot labels without treating a later interactive view as an exact historical reference.
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