Build a useful investigation brief
Trace record creation
Map the registration response to the verification record, expiry metadata, and pending page. Confirm which identifier safely correlates the record without copying the token. Compare a first send with a resend and note whether the prior record remains valid, replaced, or unknown.
Follow link routing
Use a synthetic link through the intended verification route and record the resulting state, redirect, and session. Exercise expired, already-used, and malformed fixtures if supported. Check whether an old link shows an actionable message rather than a blank or unrelated page.
Separate delivery limits
Compare application handoff evidence with the mailbox or provider observation available in the local test boundary. Do not claim delivery from enqueue alone. Record timing, retries, address correction, and session state so an application bug is not hidden behind an external unknown.
What to carry forward
The investigation is ready when one registration variant can be followed through record, message handoff, link route, expiry, and resulting session, with secrets excluded. Deliver the first divergence and state the provider or mailbox boundary that remains unobserved.
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