Aglet

Prioritize a broken deep link in a critical workflow

A broken deep link can strand users in a routine review or break an important handoff. Prioritize links that carry a decision, record, or filtered queue context, especially when users cannot reconstruct the destination easily.

Decide where the work belongs

  1. Rank destination importance

    Describe whether the link opens a signal, work item, deployment, review, setup step, or secondary page. Give higher priority to shared records and actions that require precise context.

  2. Rank recovery effort

    Check whether users can reach the same record through navigation or search and whether filters, tab, or page state can be reconstructed. Context loss still matters when the record exists.

  3. Set a link checkpoint

    Choose a review after route, identifier, redirect, or context-preservation changes. State the expected final path and selected state that will decide whether the link is trustworthy.

What to carry forward

The queue decision should name destination, context loss, affected roles, owner, and checkpoint. Keep priority high when a valid record is hidden behind a broken handoff or users cannot rebuild the intended review state. Prioritize links that arrive from repeated notifications, search, or shared review flows and strand users before a primary decision; a rare malformed link may remain scoped.

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