Establish what is happening
Capture the operation handle
Record batch size, submission time, environment, operation identifier, and initial response without copying sensitive records. Note whether the response means accepted, queued, running, complete, or failed. Preserve local state beside each status read.
Follow progress and results
Poll or read the documented status path at bounded intervals. Compare status timestamps, completed and failed counts, result link, and local reconciliation. A complete status without result evidence may be a retrieval gap rather than complete business work.
Bound batch impact
Group operations by size, endpoint, status path, client revision, and partial-result state. Separate duplicate submission, slow progress, expired results, and wrong-handle lookup. Keep records that are pending or partially reconciled visible for review.
What to carry forward
Triage ends with one operation lifecycle, result count, local state, and recovery gap. Stop duplicate submissions while status is uncertain. Route submission, polling, and reconciliation questions separately. Keep pending records out of the completed count.
Technical background: GitHub 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