Skip to main content
← Back to list
01Issue
BugShippedSwamp CLIPublic
Assigneeszack

Relationships

#4691 A dense schedule fires nothing during the repeated hour after a DST fall-back

Opened by zack · 11/12/2026· Shipped 11/12/2026

Summary

In negative-offset zones (all US zones), a schedule denser than hourly fires nothing during the repeated hour after a DST fall-back. */5 * * * * * in America/Chicago fires up to 06:59:55Z and then not again until 08:00:00Z, skipping the 720 slots of the second 01:00-01:59 (CST). The same holds for */15 * * * * (06:45Z, then 08:00Z).

Cause

Both the live scheduler (WorkflowScheduler, after swamp-club#4687) and catch-up (evaluateMissedFires, after swamp-club#4666) walk slots with nextSlotAfter in src/domain/workflows/cron_slots.ts, which follows croner's own chain. croner maps a local wall time in the repeated hour to its first (CDT) occurrence, so its chain goes from 01:59:55 CDT straight to 02:00 CST and the second copy of the hour has no slots.

History

Before swamp-club#4687 the same skip already happened for a schedule running through the fall-back, since croner's own timer followed that chain. Only a schedule armed inside the repeated hour (serve start, leadership promotion, reload, override change) fired there: croner's timer measured from a nextRun behind now and fired on every wake, which was the hot loop #4687 fixed. With #4687 the skip applies however the schedule was armed.

Expected

Wildcard and interval fields fire through both copies of the repeated hour, as vixie cron does, while a fixed-time slot (for example 30 1 * * *) still runs once on the fall-back day. The live timer and catch-up must keep using one slot definition, so the change belongs in nextSlotAfter (or a successor) rather than in either caller. Positive-offset zones (Europe/London), where croner skips the first copy of the hour instead, should be covered by the same rule.

Reproduction

With the fake clock from src/domain/workflows/schedule_dst_test_helpers.ts, construct new WorkflowScheduler({ timezone: "America/Chicago", clock }) at 2026-11-01T06:50:00Z, register */5 * * * * *, start it and advance to 08:00:10Z: no fire lands between 07:00Z and 08:00Z.

02Bog Flow
✓OPEN✓TRIAGED✓IN PROGRESS✓SHIPPED+ 1 MOREASSIGNED+ 5 MOREREVIEW+ 6 MOREPR_LINKED+ 2 MORESESSION_SUMMARIZED

Shipped

11/12/2026, 10:02:39 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
zack assigned zack11/12/2026, 9:11:03 PM

Sign in to post a ripple.