Aglet

Triage a broken deep link with its context intact

Deep links carry more than a destination: they may preserve project, filters, tabs, pagination, or a record identity. Start with the exact link and expected landing state, then distinguish an invalid resource from lost navigation context.

Establish what is happening

  1. Preserve the link contract

    Record path, query, fragment, record identifier, source page, and expected title or selected state. Redact credentials or private payloads while keeping routing structure intact.

  2. Follow the failure

    Open the link from a fresh session and a signed-in session where appropriate. Capture status, redirect chain, final URL, flash or empty copy, and the first point where expected context disappears.

  3. Bound affected users

    Check whether the failure depends on role, project membership, archived state, browser history, or link age. Separate an intentionally unavailable record from a route that loses a valid destination.

What to carry forward

Triage should state the link contract, expected landing state, first routing failure, and user consequence. Escalate when a valid shared path cannot be recovered; otherwise classify an expired or intentionally inaccessible record separately. Preserve the exact URL shape and entry context, including query parameters and record identity, then state whether the destination is missing, unauthorized, filtered away, or malformed.

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