Cron scheduler guard leak and lifecycle handling
Cluster 86482 · cron. Data as of
Nothing open on GitHub. Fix merged in #86682 on 15 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #86682. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #86682. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These members address a bug where an unsuccessful create_execution call leaves a cron job permanently stuck in the running set, and introduce changes to prevent the resulting guard leak and improve scheduler lifecycle robustness.
Open issues0
Open PRs0
Fixes on record
-
#70638 fix(cron): make Trigger now execute immediately and safely
files:
apps/desktop/src/app/chat/sidebar/cron-jobs-section.tsx,apps/desktop/src/app/chat/sidebar/index.tsx,apps/desktop/src/app/contrib/wiring.tsx,apps/desktop/src/app/cron/cron-actions.test.ts,apps/desktop/src/app/cron/cron-actions.ts,apps/desktop/src/app/cron/index.tsx,apps/desktop/src/app/session/hooks/use-session-list-actions.ts,apps/desktop/src/hermes.test.ts,apps/desktop/src/hermes.ts,apps/desktop/src/store/cron.test.ts,apps/desktop/src/store/cron.ts,apps/shared/src/cron-trigger-controller.ts,apps/shared/src/index.ts,cron/executions.py,cron/jobs.py,cron/scheduler.py,cron/scheduler_provider.py,gateway/platforms/api_server.py,gateway/run.py,hermes_cli/web_routers/cron.py(+25 more) -
#86682 fix(cron): consolidate scheduler-lifecycle salvage — guard-leak tick continuation, failure alerts, DNS fallback, bounded cleanup, CLI background verdict
files:
contributors/emails/[redacted:email],cron/scheduler.py,hermes_cli/cron.py,tests/cron/test_cleanup_timeout.py,tests/cron/test_parallel_pool.py,tests/cron/test_recurring_wedge_selfheal.py,tests/cron/test_run_one_job.py,tests/cron/test_scheduler.py,tests/hermes_cli/test_cron.py,website/docs/user-guide/features/cron.md
1 PR closed without merging
From the close comments: merged via another change 1
-
#86582 fix: avoid cron guard leak on create_execution failure · merged via another change →
#86682,#70638
Closed issues · 1
- Closed#86482cron scheduler: create_execution failure strands job in running set forever ('already running — skipping' every tick)
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.50: 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 Lab