Decide where the work belongs
Name the blocked action
Record whether users cannot continue, choose another file, inspect metadata, or approve the selection while preview generation runs. Note preparation effort and whether the delay causes abandonment or repeated selection.
Map affected file paths
List formats, dimensions, orientations, multi-file selections, and error cases where the delay appears. Mark whether generation occurs locally, after transfer, or during a separate stage, using observations rather than assumptions about implementation.
Choose the queue
Queue readiness design when preview unnecessarily blocks the workflow, generation investigation when work is unexpectedly repeated or slow, or pending-state repair when continuation is safe but invisible. Attach selection and ready timestamps.
What to carry forward
Prioritize the delay when it blocks a consequential selection or makes people repeat work without knowing whether the file is still active. A clearly labeled pending preview that permits safe continuation can rank behind hidden or destructive delay behavior.
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