Aglet

Learn from recurring file size limit confusion

Repeated size questions usually combine hidden rules, ambiguous units, and late enforcement. Learning should preserve the boundary files that exposed each issue and record the context and action needed, so future changes to validation or copy keep size eligibility discoverable.

Keep the lesson for the next incident

  1. Cluster the limit cases

    Group findings by unit labels, rounding, workflow context, early guidance, transfer-stage rejection, and missing reduction advice. Record raw bytes and the user decision each message enabled or blocked.

  2. Document size semantics

    State the measured quantity, units, rounding, applicable workflow, enforcement boundary, and recovery action. Include below, exact, and above examples so the rule remains testable and context-specific limits are not flattened.

  3. Trigger boundary review

    Require the fixtures when changing upload limits, file classes, picker guidance, validation, or processing. Assign an owner for size language and note any separate limit that must be shown when the workflow context changes.

What to carry forward

The learning record is useful when size is defined in raw bytes and displayed units, every context has a known boundary, and recovery advice is tested. If a limit cannot be enforced early, make the late boundary explicit before users transfer a file.

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