Aglet

Triage a file size limit discovered after transfer

A file may be rejected before transfer, after bytes move, or during later processing, and users cannot plan around a limit that appears only at the end. Triage should record the file size, every visible constraint, rejection boundary, and the action offered after rejection.

Establish what is happening

  1. Record the file and limit

    Capture the file's measured size, units displayed, selected source, and any limit text visible before transfer. Note rounding, decimal or binary labels, and whether the limit differs by workflow or file type.

  2. Trace when rejection appears

    Record picker, client, receiver, validation, and processing responses in order. Identify the first boundary that knows the file is too large and compare it with the earliest place a user could reasonably decide whether to proceed.

  3. Classify the communication gap

    Classify the case as absent limit, inconsistent units, late validation, workflow-specific rule, or misleading retry. State whether the file could be reduced or replaced and what evidence supports that next action.

What to carry forward

Triage is complete when measured size, stated limit, units, and rejection boundary are documented for one file. If limits vary by context, record the context explicitly instead of presenting one global threshold as the explanation.

Technical background: MDN 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