Aglet

Prioritize late file size limits by wasted transfer effort

A late size rejection is costly when a large file takes meaningful time to transfer or is difficult to recreate. Prioritization should weigh where the limit is discoverable and whether the next action is obvious, separating a copy omission from a limit that changes by context.

Decide where the work belongs

  1. Quantify observed effort

    Record file class, measured size, transfer stage reached, time or work spent before rejection, and whether a retry could succeed. Use the actual case rather than an assumed network speed or guessed audience volume.

  2. Assess discoverability

    List the places a user can learn the limit: selection guidance, form copy, progress state, response, and processing result. Mark conflicting units or workflow-specific rules that could make an early message misleading.

  3. Select the repair queue

    Queue early eligibility communication when the rule is known but hidden, unit clarification when labels disagree, or enforcement investigation when rejection boundaries differ from the documented limit. Attach a boundary-sized fixture and the observed message.

What to carry forward

Prioritize the issue when users repeatedly transfer files that the workflow could have rejected or explained earlier, especially near a decision deadline. A visible, accurate limit with a workable reduction path can rank below hidden rejection after expensive transfer.

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