Aglet

Prioritize scheduled timezone drift by missed calendar consequence

Timezone drift matters when a run crosses a local business boundary or creates a duplicate action, not simply because its UTC timestamp looks unfamiliar. Prioritize the calendar consequence and the number of occurrences exposed. An isolated display mismatch with correct execution has a different queue position from a run that fires on the wrong local date.

Decide where the work belongs

  1. Name the calendar consequence

    For each occurrence, record whether it ran early, late, twice, or not at all relative to the intended local rule. Identify the action the run was meant to perform. Put a wrong-date durable action ahead of a label that only confuses the next-run display.

  2. Group by rule and boundary

    Compare ordinary dates, offset-transition dates, and schedules whose rule or zone changed. Note which occurrences share the same stored configuration and which do not. A boundary-specific issue should not automatically reprioritize every recurring job.

  3. Choose a bounded calendar check

    Select immediate investigation, a rule correction with occurrence reconciliation, or evidence collection for one neighboring run. State the missing zone or persisted due value that changes priority. Avoid editing the schedule repeatedly until the original rule and run history are captured.

What to carry forward

Queue the issue with the local consequence, occurrence IDs, rule and zone evidence, and duplicate or missed-run risk. Escalate when a wrong local date triggers durable work. Otherwise schedule a conversion investigation across one calendar boundary and preserve the intended local rule.

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