Cron + /model consistency fix: verify isolated jobs actually use your model override
Scenario: /model or /switch reports success, but scheduled isolated runs still use default model. Apply upgrade with a canary cron job and validate run-time model selection in history/logs.
GITHUBDiscovered 2026-02-14Author @shtse8
Prerequisites
- You have isolated cron jobs that use payload.kind=agentTurn.
- You can set model override with /model (or session_status override) and inspect job runs.
Steps
- Upgrade OpenClaw to a build containing PR #14983, then restart gateway.
- In the target session, set an explicit model override (example: Codex 5.3 alias).
- Create/trigger a short-interval isolated cron job and let it run at least once.
- Check cron run output/session traces to confirm the run used the overridden model, not default.
Commands
openclaw gateway statusopenclaw gateway restartopenclaw cron listopenclaw cron run <jobId>openclaw cron runs <jobId>Verify
Cron run history and resulting session behavior align with the configured model override across repeated runs.
Caveats
- Alias resolution may differ by provider; if unsure, test with full provider/model id once（需验证）.
- Main-session systemEvent jobs are a different path; do not mix verification conclusions.
Source attribution
This tip is aggregated from community/public sources and preserved with attribution.
Open original source ↗