Keep the lesson for the next incident
Document the schedule contract
Describe schedule identity, calendar and timezone interpretation, due-run creation, enqueue and claim, execution, dependencies, commit, retry classes, missed-window behavior, overlap rule, final visibility, and idempotency. Explain which outcome is customer-visible and which records prove completion.
Keep a recurring-run journey
Preserve checks for normal due run, dependency failure, delayed claim, missed window, retry, safe replay, overlap, next occurrence, and final state. Define expected identifiers and timing. Assign ownership for interpreting a missed run and updating the journey when calendar behavior changes.
Recheck after schedule or worker changes
Review representative runs after timezone, calendar, scheduler, queue, worker, lock, retry, dependency, or output changes. Compare due time, execution, overlap, idempotency, and continuity again. Add a distinct case when a schedule has different urgency or recovery rules instead of generalizing one cadence.
What to carry forward
The learning record should retain schedule identity, calendar and timezone rules, due and execution boundaries, overlap and retry ownership, recovery checks, and recurrence triggers. It is complete when future engineers can distinguish missed scheduling from failed execution and verify one safe recurring outcome.
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