Keep the lesson for the next incident
Document outcome and retry meaning
State which outcomes are accepted, rejected, skipped, or unresolved and how each enters the retry flow. Explain whether corrected files retain a relationship to the original attempt. Keep the confirmation copy aligned with these rules so users understand the exact work the next attempt will execute.
Retain a two-attempt example
Keep a small mixed-outcome fixture, its correction, and the expected record identities after both attempts. Include an already accepted row and a remaining failure. Record why overall counts are insufficient so future checks preserve per-row comparison rather than simplifying the example into one successful retry status.
Review changes to recovery inputs
Assign review when source identity, corrected-file handling, matching, or retry selection changes. Inspect the outcome report and final state together. Track confirmed repeated acceptance separately from ordinary validation failures, and keep interrupted attempts with unknown durable outcomes available for investigation rather than hiding them in a completed summary.
What to carry forward
Close with an explicit retry contract, a readable two-attempt fixture, and an owner for recovery changes. Preserve limits around unknown state and historical reconciliation. The next operator should be able to determine what remains before retrying, without guessing from a failed job label or manually reconstructing accepted rows from memory.
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