Decide where the work belongs
Rank the outcome missed
Name the report, synchronization, reminder, cleanup, projection, or state update the schedule should produce. Separate delayed low-impact maintenance from a recurring action that affects decisions or customer communication. Give higher priority to missed work with no trustworthy indication it failed.
Group recurrence and schedule reach
Compare schedule identity, due window, timezone, input size, dependency, worker, release, overlap, retry count, and final status. Distinguish one calendar edge from repeated failure across ordinary runs. Include upcoming due runs when recovery work could collide with normal execution.
Choose a bounded recovery slice
Select immediate investigation, a scheduler or execution correction, or collection of one missing due-to-outcome trace. State what changes priority, such as an approaching customer deadline or unsafe replay. Keep historical backfill separate from making the next scheduled run trustworthy.
What to carry forward
Produce a queue decision tied to missed outcome, recurrence, upcoming schedule, overlap risk, and evidence quality. Include whether replay is safe. The next engineer should have one schedule identity and due window to reproduce plus a clear reason it outranks other background work.
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