Cairn
NousResearch/hermes-agent

Cron manual trigger swallowed by timezone repair pass

Cluster 78516 · cron. Data as of

2 open items. Fix attempted, not merged.

The short answer

0open issues
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
0 issues and 2 PRs.

A bug where triggering a cron job manually via the dashboard was silently discarded when the host timezone differed from UTC, because a timezone repair pass recomputed next_run_at to the next scheduled occurrence. The members include the bug report and related fixes.

Open issues0

No open issues.

Open PRs2

  • PR#78579fix(cron): skip TZ migration repair for manual trigger (#78516)
  • PR#78620fix(cron): stop the timezone repair pass from swallowing manual triggers
Closed issues · 1
  • Closed#78516[Bug]: Cron dashboard "Run now" is swallowed on recurring jobs when host TZ != UTC (next_run_at recomputed to next occurrence)
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.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
Closed issues
1
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/78516.json
cluster/78516.md