Aglet

Investigate Partial Import Retry Selection

Investigate retry scope with a fixture that produces a deliberate mix of accepted and rejected records. Give each source row a distinct identity and preserve every attempt’s selection. The useful comparison is between durable first-attempt outcomes and second-attempt inputs, not merely between two overall job statuses.

Build a useful investigation brief

  1. Create a mixed-outcome fixture

    Prepare a small file with valid rows and one predictable validation failure. Record expected first-attempt outcomes independently. Where interruption behavior is in scope, use a controlled case and inspect durable state before retrying; do not assume a cancelled or failed request reversed work that had already committed.

  2. Trace the retry input contract

    Inspect how the next attempt selects rows and carries source identity, corrections, and original outcome references. Compare full-file retry with any failed-row-only path supported by the product. Check whether a corrected export changes ordering or identifiers in a way that makes the selection contract ambiguous.

  3. Compare second-attempt assignments

    Execute the controlled retry and inspect each destination outcome. Identify the first mismatch between intended selection and actual work. Separate selection bugs from destination matching behavior, since selecting the right failed row can still produce an incorrect update if its identity is interpreted differently during the second attempt.

What to carry forward

Deliver a two-attempt timeline with source identities, durable outcomes, selected retry inputs, and observed assignments. Propose a bounded change at the first mismatch. Keep unknown first-attempt outcomes explicit; a retry policy cannot be demonstrated safe by relabeling uncertain records as failed and assuming they were never accepted.

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