Skip to content

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

Closed
ygd58 wants to merge 2 commits into
NousResearch:mainfrom
ygd58:fix/cronjob-schedule-required-grok
Closed

fix(cron): clarify schedule is required for create in tool schema#32448
ygd58 wants to merge 2 commits into
NousResearch:mainfrom
ygd58:fix/cronjob-schedule-required-grok

Conversation

@ygd58

@ygd58 ygd58 commented May 26, 2026

Copy link
Copy Markdown
Contributor

Problem

Grok models omit schedule when calling cronjob action=create (issue #32427).

Two-layer fix

  1. Description text: REQUIRED for action=create
  2. JSON Schema if/then conditional required

Fixes #32427

ygd58 added 2 commits May 26, 2026 08:35
Grok models (and other LLMs) sometimes omit the schedule parameter
when calling the cronjob tool with action=create because the schema
only listed 'action' in required[] and the schedule description did
not explicitly state it was mandatory (issue NousResearch#32427).

Fix: update schema descriptions to clearly state schedule is REQUIRED
for action=create, making this explicit for models that rely on
description text for parameter compliance.

Fixes NousResearch#32427
…eate

Previous commit updated descriptions but left required[] with only
'action'. Add JSON Schema if/then so schema-strict models also see
schedule and prompt as required when action=create.

Two-layer fix:
1. Description text (for description-driven models like Grok)
2. if/then conditional schema (for schema-strict validators)
@alt-glitch alt-glitch added type/bug Something isn't working P3 Low — cosmetic, nice to have comp/cron Cron scheduler and job management comp/tools Tool registry, model_tools, toolsets provider/xai xAI (Grok) labels May 26, 2026
@teknium1

Copy link
Copy Markdown
Contributor

Merged via #32804 — your description-text commit was cherry-picked onto current main with authorship preserved in git log (commit 5101326). Dropped the if/then JSON-Schema layer (Gemini's allowlist strips it, Anthropic doesn't enforce it, and Grok ignores schemas anyway — the description text is the layer that actually moves it). Thanks for the fix and the clean repro on the issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

comp/cron Cron scheduler and job management comp/tools Tool registry, model_tools, toolsets P3 Low — cosmetic, nice to have provider/xai xAI (Grok) type/bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

cronjob tool fails to include required schedule parameter when using Grok models

3 participants