Skip to content

Cron jobs ignore model specification in payload #10602

@vera-clawbot

Description

@vera-clawbot

Summary

Cron jobs with a specific model in the payload are ignoring that specification and falling back to what appears to be an internal default fallback chain that differs from both the specified model AND the configured agent defaults.

Observed Behavior

Job hourly-stage1-r1-analysis specifies:

"model": "openrouter/deepseek/deepseek-r1"

But when run, the error shows it tried:

anthropic/claude-sonnet-4-20250514
anthropic/claude-opus-4-6

Neither of these is the specified model OR the configured default fallback (anthropic/claude-opus-4-5openrouter/deepseek/deepseek-r1).

Direct API Tests

Both models work fine when tested directly:

Config (relevant parts)

"models": {
  "providers": {
    "openrouter": {
      "baseUrl": "https://openrouter.ai/api/v1",
      "apiKey": "...",
      "models": [{"id": "deepseek/deepseek-r1", ...}]
    }
  }
},
"agents": {
  "defaults": {
    "model": {
      "primary": "anthropic/claude-opus-4-5",
      "fallbacks": ["openrouter/deepseek/deepseek-r1"]
    }
  }
}

Expected Behavior

Cron jobs should use the model specified in payload.model, with the configured fallback chain if that model fails.

Environment

  • OpenClaw: 2026.2.3-1
  • OS: macOS 26.2 (M4)

Related

Possibly related to #5533 (meta.lastTouchedAt)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions