# NousResearch/hermes-agent · Cron repeat jobs incorrectly marked completed early

## Open now

- 0 issues, 1 PR open on GitHub.
- PR #29811: fix(cron): reschedule one-shot jobs with remaining repeats instead of marking completed

A bug where repeating cron jobs are prematurely marked as completed after their first run, along with related fixes to reschedule such jobs correctly based on remaining repeats.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 1 open PR(s), 0 merged PR(s), 1 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. 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

- #29392: \[BUG\] Scheduler prematurely marks repeating cron jobs as 'completed' after first successful run

## Prior & competing PRs

- **#29455: fix(cron): promote "2m" + repeat>1 to recurring interval (#29392)**. closed without merge
  - maintainer direction: category `partial_fix`; implication `needs_llm`; refs `#29392`
- **#29811: fix(cron): reschedule one-shot jobs with remaining repeats instead of marking completed**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`
  - files: `agent/agent_init.py`, `agent/conversation_loop.py`, `cron/jobs.py`, `hermes_cli/auth.py`, `hermes_cli/config.py`, `run_agent.py`

## Fix status

- No merged fix on record.
- Subsystem: `cron`