Aglet

Prioritize missed scheduled runs by commitment and recovery risk

A missed run is urgent when it represents a time-bound obligation or leaves an expected state unmaintained. A late occurrence with an explicit replay path can be scheduled differently from one whose original side effects are unknown. Prioritize commitment and recovery ambiguity together, then the breadth of the schedule family affected.

Decide where the work belongs

  1. Name the missed commitment

    Write what the occurrence was expected to update, reconcile, or produce and whether another run can safely cover it. Put a missed durable action ahead of a dashboard gap when the worker actually ran. Record any deadline or dependency that makes lateness meaningful.

  2. Compare available and unavailable workers

    Group occurrences by worker availability, queue load, and scheduler health around due time. Note whether neighboring runs succeeded through the same path. This separates a dispatch capacity gap from a schedule occurrence that was never emitted.

  3. Choose replay or investigation

    Select immediate reconciliation, a replay decision, or evidence collection for the missing handoff. State the readback needed before replay, including output and side-effect checks. Avoid creating a second occurrence while the original identity remains unresolved.

What to carry forward

Queue the occurrence with commitment, lateness, handoff evidence, and replay safety. Escalate when a due action is missing and a duplicate replay could compound effects. Otherwise schedule a focused timeline investigation with neighboring success and worker-availability controls.

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