Keep the lesson for the next incident
Cluster the timing cases
Group incidents by decode, thumbnail, metadata, render, queueing, repeated generation, and preview error. Record file characteristics, the blocked action, and the first visible state that failed to explain the wait.
Document readiness semantics
State when a file is selected, when it has a usable preview, what pending means, and which actions are allowed before readiness. Include a quick fixture, a slow fixture, a replacement, and a multi-file example.
Trigger timing review
Require the fixtures when changing preview formats, generation stages, concurrency, selection controls, or error handling. Assign an owner for pending language and record how a late result is prevented from changing a newer file.
What to carry forward
The learning record is useful when generation stages and selection readiness have separate meanings, pending actions are explicit, and contrast files remain available. If preview cannot be ready before another step, document the safe continuation boundary rather than implying that selection failed.
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