Aglet

Prioritize a Pagination Gap Investigation

Prioritizing pagination work means deciding whether to prevent data loss, repair a consumer, or clarify a changing source contract. Rank gaps by records missed and decisions affected, then consider recurrence and traversal breadth. Preserve a separate priority for duplicates or ordering defects that share the boundary.

Decide where the work belongs

  1. Rank missing consequences

    List imports, reports, synchronizations, exports, and user actions fed by the traversal. Count missed identifiers and record the concrete result they change. A small gap in a complete-data workflow may outrank a larger gap in an exploratory listing.

  2. Assess reproducibility

    Compare repeated traversals under a fixed snapshot or stable fixture. Classify the work as cursor arithmetic, offset drift, unstable ordering, mutable source, filter inconsistency, or unclear termination. Prioritize recurring deterministic gaps before a one-time difference caused by an unbounded moving set.

  3. Choose the next queue action

    Select investigate, correct a bounded consumer, define a stable traversal contract, request a snapshot, or monitor page coverage. Include first divergent page, expected population, owner, comparison method, and escalation trigger. Do not choose a broad rewrite when a narrow boundary explains the loss.

What to carry forward

Return a ranked pagination queue with missing identifiers, affected decisions, recurrence evidence, traversal breadth, owner, and next action. The leading item should name the boundary to inspect and how coverage will be compared. Keep priority provisional when source mutation prevents a stable denominator.

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