vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-06 07:00:43 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix(cron): preserve job model fallbacks

Browse Source
This commit is contained in:
Peter Steinberger
2026-04-28 00:02:14 +01:00
parent da6d8940a0
commit ff2b2e769f
8 changed files with 131 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/cli/cron.md
View File

@@ -98,9 +98,16 @@ Note: cron job definitions live in `jobs.json`, while pending runtime state live
`cron add|edit --model <ref>` selects an allowed model for the job.
<Warning>
If the model is not allowed, cron warns and falls back to the job's agent or default model selection. Configured fallback chains still apply, but a plain model override with no explicit per-job fallback list no longer appends the agent primary as a hidden extra retry target.
If the model is not allowed, cron warns and falls back to the job's agent or default model selection.
</Warning>
Cron `--model` is a **job primary**, not a chat-session `/model` override. That means:
- Configured model fallbacks still apply when the selected job model fails.
- Per-job payload `fallbacks` replaces the configured fallback list when present.
- An empty per-job fallback list (`fallbacks: []` in the job payload/API) makes the cron run strict.
- When a job has `--model` but no fallback list is configured, OpenClaw passes an explicit empty fallback override so the agent primary is not appended as a hidden retry target.
### Isolated cron model precedence
Isolated cron resolves the active model in this order: