Aglet

Investigate document link expiry across waiting and retry paths

Investigation should follow one document link through both idle waiting and active download attempts. Use a controlled short-lived case and a normal waiting case, then compare request timing and revision identity. The result should show the first boundary where the link becomes unusable or ambiguous.

Build a useful investigation brief

  1. Create timing cases

    Use a document with a known revision and capture a link immediately before use, after an idle interval, from a copied page link, and during a delayed start. Record expected same-document recovery for each case.

  2. Trace link and revision state

    Record issuance, expiry metadata, page refresh, click, request, response, renewal, and document revision at every step. Mark whether a refreshed link is bound to the original revision or only to a generic document identifier.

  3. Compare failure explanations

    Test an expired link against a valid link and a wrong-document request using the same page path. Identify the first observable difference, and leave clock skew or transport delay as hypotheses unless timing evidence supports them.

What to carry forward

The investigation is sufficient when timing cases show why the link fails and whether renewal preserves document identity. If expiry metadata or revision evidence is unavailable, deliver the observed wait-to-failure path and leave the mechanism unresolved.

Technical background: RFC Editor reference.

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