openclaw - 💡(How to fix) Fix Cron jobs fail with model allowlist rejection after config changes [1 comments, 2 participants]

Summary

Cron jobs fail with "model not in allowlist" errors when the agents.defaults.models tree gets reduced or modified.

Error Example

Model "google/gemini-3-pro-preview" is not in the allowed models list
Model "xai/grok-4-fast" is not in the allowed models list
Model "moonshot/kimi-k2.5" is not in the allowed models list

Root Cause

The model allowlist is derived from agents.defaults.models keys. When this tree is gutted (see #78296), models that cron jobs are configured to use become invalid.

Affected Jobs

Any cron job with a model assignment outside the minimal Anthropic set:

• Heartbeat jobs using ollama/gemma4:e4b
• Research jobs using xai/grok-4-fast
• Content jobs using moonshot/kimi-k2.5
• Image jobs using google/gemini-3-pro-image-preview

Expected Behavior

1. Model allowlist should remain stable across restarts
2. If a model is removed, cron jobs should either:
   • Fall back to a valid model with a warning
   • Skip execution with a clear error (not silent failure)

Current Behavior

Jobs silently fail or skip with cryptic allowlist errors. No automatic recovery or fallback.

Related

• #78295 (config persistence)
• #78296 (model tree gutting)