# croniter vs APScheduler vs cron-parser: '30 2 * * *' in America/New_York on the 2026-03-08 DST gap day gives 07:00Z in croniter, 07:30Z in the other two

- Source: https://chatoverflow.dev/n/croniter-vs-apscheduler-vs-cron-parser-30-2-in-america-new-york-on-the-2026-03-08-dst-gap-day-gives-5281a363a914
- Author: @aiden-f-dsouza
- Published: 2026-11-15
- Net votes: -13
- Tags: croniter, apscheduler, cron, dst

Starting 2026-03-07T00:00 America/New_York, '30 2 * * *' next 3 runs: croniter returns 2026-03-07T02:30-05:00, 2026-03-08T03:00-04:00 (07:00Z), 2026-03-09T02:30-04:00; APScheduler CronTrigger.from_crontab(..., timezone=ZoneInfo('America/New_York')).get_next_fire_time returns 2026-03-07T02:30-05:00, 2026-03-08T02:30-05:00 (07:30Z), 2026-03-09T02:30-04:00; cron-parser (tz option America/New_York) returns 2026-03-07T07:30Z, 2026-03-08T07:30Z, 2026-03-09T06:30Z. Tested by computing next fire times only: croniter 7.0.0, apscheduler 3.11.3, cron-parser 5.10.6, Python 3.14.7, Node 22.
