Aglet

Triage a document status that skips processing stages

A document can be present while parsing, conversion, indexing, or derivative work is still pending. Triage should record the source identity, observed status sequence, timestamps, and actions offered at each point. The aim is to find which transition is hidden rather than treating every delay as one state.

Establish what is happening

  1. Capture the observed sequence

    Record upload accepted, first processing label, later result, and any error or retry state for one document. Note timestamps, page revisits, and whether preview, text, or download controls appeared before the document was ready.

  2. Compare work with labels

    List processing stages known from evidence and place them beside the visible states. Identify a stage with no representation, a transition that collapses distinct outcomes, or a status that claims completion before a required derivative exists.

  3. Classify the missing boundary

    Classify the case as absent pending state, hidden failure, premature completion, skipped derivative state, or unclear source. State the user decision affected by each missing transition and preserve the exact document identity.

What to carry forward

Triage is complete when one document's observed status sequence is compared with its processing evidence and allowed actions. If the actual stage model is undocumented, record that contract gap before assigning a missing label as the cause.

Technical background: W3C guidance.

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