Build a useful investigation brief
Reconstruct one occurrence
Collect the schedule rule, occurrence ID, due timestamp, scheduler tick, enqueue request, queue record, and any expiration or skip state. Compare the missing occurrence with the immediately previous and next successful IDs. Keep absent records explicit and time-bounded.
Exercise the due-to-enqueue boundary
Run a sanitized schedule through a due interval with workers available, then repeat with the enqueue path delayed. Trace whether the occurrence is persisted before enqueue and whether a retry can create another ID. Preserve the schedule revision in both runs.
Test explicit recovery state
Exercise one replay, skip, or review path only after checking the original occurrence and output identity. Compare the resulting audit with a normal run. If worker unavailability merely delays claim, keep it separate from a scheduler emission failure.
What to carry forward
Deliver the missing occurrence timeline, neighboring comparison, first absent handoff, and tested recovery path. State whether scheduler emission, queue dispatch, worker capacity, or visibility is responsible for the next investigation. Keep replay safety and unresolved original state explicit.
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