Decide where the work belongs
Rank the reader consequence
For each missing output, record what the reader or dependent step was trying to do and whether the job’s source input remains available. Put an output that gates a release or reconciliation ahead of a convenience preview. Keep actual blocked actions distinct from assumed inconvenience.
Group by retention and read delay
Compare immediate readers, delayed readers, slow downloads, and outputs whose creation itself was late. Note whether expiry followed policy. A reader that requests after a clearly documented window needs a different response from an object that vanished early.
Choose recovery or retention work
Select immediate rebuild or reconciliation, a retention-policy review, or evidence collection for one output class. Name the output identity and expiry evidence required before rerunning. Do not extend retention globally without checking storage cost and reader behavior for other classes.
What to carry forward
Queue the issue with lost-work consequence, output class, reader delay, expiry evidence, and rebuild safety. Escalate when completed work has no recoverable source or blocks a consequential action. Otherwise schedule a retention and reader-contract review with immediate read and delayed-read fixtures.
Technical background: Rails guides.
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