Cairn

Cronjob tool missing/invalid parameter bugs and fixes

NousResearch/hermes-agent · cluster 6709 · cron

Data as of

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

The short answer

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

Multiple bug reports and fix attempts around the cronjob tool failing due to missing or unrecognized required parameters (schedule, model, repeat), with several schema and alias improvements proposed to address these issues.

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.

  • #32804 fix(cron): clarify schedule is required for create in tool schema

    merged to main

    files: tests/cron/test_cronjob_schema.py, tools/cronjob_tools.py

9 PRs closed without merging

From the close comments: superseded by another PR 3 · done elsewhere 2 · merged via another change 2 · duplicate 1 · other 1

  • #6758 fix(cron): forward model overrides on create · superseded by another PR → #53322
  • #7589 fix(cron): coerce repeat parameter to int to prevent TypeError · merged via another change → #7513
  • #32448 fix(cron): clarify schedule is required for create in tool schema · merged via another change → 5101326, #32804
  • #33980 fix(cron): add schedule to required array in CRONJOB_SCHEMA · duplicate → #32804, #32448, #32427
  • #34173 fix(tools): improve cronjob tool descriptions to prevent missing required params · done elsewhere → 5101326, #32448
Show 4 more
  • #34255 fix(cronjob): accept schedule param aliases (cron, when, ...) (#34120) · other
  • #34483 fix(tools): clarify cronjob required-params to prevent missing-schedule errors · done elsewhere → 5101326, #32448
  • #49792 fix(cronjob): add schedule and job_id to JSON schema required array · superseded by another PR → #53246, #34120
  • #53246 fix(cronjob): accept schedule param aliases (cron, when, ...) (#34120) · superseded by another PR → #34255, #34120, #49792
Closed issues · 5
  • Closed#6709Cron Create Fails with Model Parameter (TypeError)
  • Closed#32427cronjob tool fails to include required schedule parameter when using Grok models
  • Closed#34120[Bug]: cronjob tool: create action always fails with "schedule is required for create" even when parameters are provided
  • Closed#35636cronjob create fails / loops when passing model override parameter
  • Closed#49695Bug: cronjob tool create action fails with 'schedule is required for create' (v0.17.0)
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.12: 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
#32804
Closed issues
5
Attempts
9 PRs closed without merging
Fix link checked
26 May 2026

For your agent

The same facts, typed.

cluster/6709.json
cluster/6709.md