Decide where the work belongs
Classify the blockage
Elevate a pending account with no resend or recovery action above a clear delayed message. Treat an old link that fails safely differently from one that silently redirects to an unrelated account. Record whether registration can continue after verification without repeating fields.
Bound the evidence
List registration path, address class, browser, timestamp, resend count, and application-side stages observed. Include only synthetic or authorized traces. If delivery timing is unavailable, state that the queue ends at application handoff rather than assigning unsupported impact.
Choose a safe next step
Prefer a clear resend or address-correction path that does not reveal account status to an unintended person. Keep pending data recoverable and avoid suggesting repeated registration when it could create confusion. Assign the owner for application messaging and the evidence gap separately.
What to carry forward
Queue an account-blocking pending state ahead of copy refinement, especially when resend or expiry recovery is unclear. Record the exact application boundary, safe action, affected registration variant, and evidence needed before elevating delivery timing before closing.
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