Establish what is happening
Capture the visible state
Record the registration time, verification-page message, address domain class, resend control, and link result using a synthetic account. Note whether the person can sign in or remains pending. Redact the address and preserve no token, cookie, or message body in screenshots.
Trace the message stages
Compare registration response, verification-record creation, mail enqueue evidence, delivery result available to the test environment, link request, and expiry state. Mark each stage observed, unavailable, or unknown. A queued message does not prove delivery or successful verification.
Repeat safe variants
Use a fresh synthetic address, a resend, an old link, an expired fixture, and a wrong-address correction path if supported. Keep attempts isolated and note timing. Do not treat a missing provider-side observation as evidence that the application failed to send.
What to carry forward
Triage is complete when the pending state, observed message stages, link outcome, and safe recovery action are recorded. If delivery cannot be observed locally, classify it as an evidence boundary and keep application state separate from provider or mailbox conclusions.
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