# NousResearch/hermes-agent · Cron next_run_at wrong offset from foreign timezone

## Open now

- 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.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #99496. Verify it addresses your case.
- **Recommended:** read PR #99496 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-99496`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Closed / duplicate issues

- #97905: Cron: \`next_run_at\` computed under a foreign process's timezone persists wrong-offset fire times into profile jobs.json

## Prior & competing PRs

- **#99496: fix(cron): profile-keyed atomic timezone cache stops wrong-offset next_run_at persistence (salvage #92489)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_time.py`, `tests/cron/test_cron_next_run_profile_timezone.py`, `tests/test_timezone.py`
- **#97961: fix(cron): re-resolve hermes_time per profile in multiplex ticker**. closed without merge
  - maintainer direction: category `volume_quota`; implication `active`; refs `#92489`, `#97491`

## Fix status

- Merged to main in PR #99496 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-08-31`.