hermes - 💡(How to fix) Fix cronjob create fails / loops when passing model override parameter

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

  • Result: Persistent "schedule is required" error + repeated failure warning after 3+ attempts
RAW_BUFFERClick to expand / collapse

When attempting to create a cron job with a specific model override using the model parameter, the tool repeatedly fails with "schedule is required for create" even when schedule (and prompt) are provided. This triggers Hermes' repeated failure detection loop.

Reproduction

  • Using cronjob tool with action=create
  • Passing model={"model":"grok-build-0.1","provider":"xai"} along with valid schedule and prompt
  • Result: Persistent "schedule is required" error + repeated failure warning after 3+ attempts

Expected behavior

The model override should work (it is already used successfully in existing cron jobs, e.g. the GoCall nightly job uses grok-build-0.1).

Additional context

  • delegate_task has no equivalent model parameter, so there is currently no way to run delegated tasks on a specific model.
  • This appears related to known schema/tool-calling fragility with certain models (notably grok-4.3).

Impact

Users cannot reliably schedule jobs against specific models/providers via the cronjob tool.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

The model override should work (it is already used successfully in existing cron jobs, e.g. the GoCall nightly job uses grok-build-0.1).

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - 💡(How to fix) Fix cronjob create fails / loops when passing model override parameter