Cairn
NousResearch/hermes-agent

Cron claimed_at UTC timestamp ordering fixes

Cluster 86520 · cron. Data as of

Nothing open on GitHub. Fix merged in #88337. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #88337. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #126258. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and PRs address problems with how cron execution timestamps are stored and sorted, specifically that offset-bearing ISO strings cause incorrect lexicographic ordering across DST and timezone boundaries. Changes involve storing claimed_at in UTC and correcting sort behavior in the execution ledger.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #88337 fix(cron): clear run_claim for one-shot jobs on dispatch failure (salvage #87591)

    merged to main

    files: cron/jobs.py, cron/scheduler.py, tests/cron/test_oneshot_dispatch_failure_run_claim.py

  • #126258 fix(cron): execution, delivery and incident history ordered by instant, not by text (#86520)

    merged to main

    files: cron/delivery_queue.py, cron/executions.py, cron/incidents.py, tests/cron/test_cron_incidents.py, tests/cron/test_delivery_queue.py, tests/cron/test_execution_ledger.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1

  • #86889 [verified] fix: sort cron execution ledger by UTC claimed timestamp · superseded by another PR → 318f6ac, #126258
  • #87623 fix(cron): call-time store paths, UTC claimed_at, one-shot run_claim release · done elsewhere → #86522, #88337, #87591
Closed issues · 1
  • Closed#86520cron executions: claimed_at stored as offset-bearing ISO string, lexicographic ORDER BY diverges from absolute time across DST/timezone changes
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.40: the share of item 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.

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 Lab

At a glance

Subsystem
cron
Merged PRs
#88337, #126258
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
28 Sep 2026

For your agent

The same facts, typed.

cluster/86520.json
cluster/86520.md