Cron next_run_at wrong offset from foreign timezone
Cluster 97905. Data as of
Nothing open on GitHub. Fix merged in #99496 on 31 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #99496. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #99496. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These members address a bug where cron job fire times are computed using another process's timezone, causing incorrect offsets to be persisted into each profile's jobs.json. The fix involves re-resolving the timezone per profile in the multiplex ticker and introducing a profile-keyed atomic timezone cache.
Open issues0
Open PRs0
Fixes on record
-
#99496 fix(cron): profile-keyed atomic timezone cache stops wrong-offset next_run_at persistence (salvage #92489)
files:
hermes_time.py,tests/cron/test_cron_next_run_profile_timezone.py,tests/test_timezone.py
1 PR closed without merging
From the close comments: PR volume cleanup 1
-
#97961 fix(cron): re-resolve hermes_time per profile in multiplex ticker · PR volume cleanup →
#92489,#97491
Closed issues · 1
- Closed#97905Cron: `next_run_at` computed under a foreign process's timezone persists wrong-offset fire times into profile jobs.json
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Merged PRs
- #99496
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 31 Aug 2026