Keep the lesson for the next incident
Cluster the expiry cases
Group incidents by idle page, copied link, delayed start, renewal loop, revision change, and missing error context. Record issuance and click timing plus the reader action that followed each failure.
Document link semantics
State what a link identifies, how its expiry is communicated, what renewal preserves, and which failures require returning to the document page. Include immediate, delayed, and copied-link examples with expected revision identity.
Add a review trigger
Require timing fixtures when changing link lifetime, issuance context, document revision handling, download start, or error copy. Assign an owner for recovery wording and note any boundary where only a new link can be promised.
What to carry forward
The learning record is complete when expiration timing, renewal behavior, and revision identity have explicit rules with representative waiting fixtures. If timing cannot be guaranteed, make the bounded use window and same-document recovery action visible to readers.
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