Decide where the work belongs
Classify the blocked result
Elevate a check that cannot submit or leaves no status above a sample that is saved but linked unclearly. Treat an invalid key, wrong environment, duplicate attempt, and processing delay as different queue classes. Record whether the owner can retry without creating ambiguity.
Bound the evidence
List project, role, key state, browser, viewport, attempt count, and visible or persisted status. Count only synthetic reproductions or identified reports. If a background transition is unobservable, state that boundary rather than inferring a failed save or successful sample.
Choose recovery
Prefer a next action that names the missing key, project context, or retry state and preserves the first attempt’s result. Do not tell a new owner to use production credentials. Assign a setup owner for local flow and a separate owner for any external intake question.
What to carry forward
Queue a check that cannot submit or explain its result ahead of copy polish, especially when the first project remains blank. Include the exact key and project state, observed scope, safe recovery, owner, and evidence required to confirm processing.
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