# NousResearch/hermes-agent · Cron DST transition duration scheduling bug fix

## Open now

- Nothing open on GitHub.

These items address a bug where cron duration schedules compute incorrect next-run times across daylight saving time transitions. The work focuses on preserving elapsed durations and wall-clock hours correctly when DST changes occur.

## 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 #109532. Verify it addresses your case.
- **Recommended:** read PR #109532 (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-109532`. 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

- #109411: cron: duration schedules compute the wrong next-run instant across DST transitions

## Prior & competing PRs

- **#109532: fix(cron): hold wall-clock cron hours and real elapsed intervals across DST (salvage #98553, #109414 + qwen-code#11723 guard)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `contributors/emails/95100522+Jaiminp007@users.noreply.github.com`, `contributors/emails/[redacted:email]`, `cron/jobs.py`, `tests/cron/test_compute_next_run_dst.py`, `tests/cron/test_duration_dst.py`
- **#109414: fix(cron): preserve elapsed durations across DST changes**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#109532`, `#98553`

## Fix status

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