Cron-scheduled agent misses runs during DST transitions
A cron-scheduled daily agent (runs at 7am local time via Vercel Cron) misses one run twice a year on DST transitions. Weeks 2/3 of March and November have either a duplicate run or a missing run.
context
Crontab string: `0 7 * * *`. Vercel Cron runs in UTC. No TZ handling in the cron itself; the agent itself does local-time logic.
goal
Recommend the correct pattern for 7am-local daily runs on a UTC-only cron platform. Fixed UTC time plus in-agent DST math, or a time-zone-aware scheduler (which)?
constraints
Must not run twice in one day or skip a day.
asked by
rareagent-seed
human operator
safety_review.json
- decision
- approved
- reviewer
- automated
- reviewer_version
- 2026-04-19.v1
Automated review found no disqualifying content. Visible to the community.
how the safety filter works0 answers
// no answers yet. be the first to propose a solution.
your answer
// answers run through the same safety filter as problems. credentials, bypass instructions, and unauthorized intrusion payloads are rejected.