openclaw - 💡(How to fix) Fix v2026.5.4: model allowlist breaks existing cron jobs using claude-haiku-4-5; claude-haiku-4-7 also unrecognised by Anthropic API [5 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#78000Fetched 2026-05-06 06:18:02
View on GitHub
Comments
5
Participants
3
Timeline
7
Reactions
2
Author
Timeline (top)
commented ×5mentioned ×1subscribed ×1

After upgrading to v2026.5.4, all cron jobs with payload.model = anthropic/claude-haiku-4-5 began failing immediately with:

cron payload.model 'anthropic/claude-haiku-4-5' rejected by agents.defaults.models allowlist: anthropic/claude-haiku-4-5

This is a silent breaking change — there is no migration path, no warning during upgrade, and no documentation on which model slugs are now valid for cron payloads.

Error Message

  1. All affected crons fail immediately on next scheduled run with the allowlist rejection error

Root Cause

After upgrading to v2026.5.4, all cron jobs with payload.model = anthropic/claude-haiku-4-5 began failing immediately with:

cron payload.model 'anthropic/claude-haiku-4-5' rejected by agents.defaults.models allowlist: anthropic/claude-haiku-4-5

This is a silent breaking change — there is no migration path, no warning during upgrade, and no documentation on which model slugs are now valid for cron payloads.

Fix Action

Fix / Workaround

  1. Have one or more cron jobs with payload.model = "anthropic/claude-haiku-4-5"
  2. Upgrade to v2026.5.4
  3. All affected crons fail immediately on next scheduled run with the allowlist rejection error
  4. consecutiveErrors increments silently — no user-facing alert
  • All lightweight crons that previously used haiku for cost efficiency are either broken or forced onto sonnet (~10x cost)
  • No automatic detection or remediation — users must manually identify and patch each cron
  • In our fleet: 7 Haderach crons affected, plus additional crons across other agents swept by fleet manager

Code Example

cron payload.model 'anthropic/claude-haiku-4-5' rejected by agents.defaults.models allowlist: anthropic/claude-haiku-4-5
RAW_BUFFERClick to expand / collapse

Summary

After upgrading to v2026.5.4, all cron jobs with payload.model = anthropic/claude-haiku-4-5 began failing immediately with:

cron payload.model 'anthropic/claude-haiku-4-5' rejected by agents.defaults.models allowlist: anthropic/claude-haiku-4-5

This is a silent breaking change — there is no migration path, no warning during upgrade, and no documentation on which model slugs are now valid for cron payloads.

Steps to Reproduce

  1. Have one or more cron jobs with payload.model = "anthropic/claude-haiku-4-5"
  2. Upgrade to v2026.5.4
  3. All affected crons fail immediately on next scheduled run with the allowlist rejection error
  4. consecutiveErrors increments silently — no user-facing alert

Expected Behaviour

Either:

  • The upgrade migrates claude-haiku-4-5claude-haiku-4-7 (or equivalent) automatically, OR
  • The upgrade documents clearly which model slugs are valid, OR
  • The default agents.defaults.models config includes a haiku-tier model out of the box so lightweight crons don't have to fall back to sonnet

Actual Behaviour

  • anthropic/claude-haiku-4-5 → rejected by allowlist
  • anthropic/claude-haiku-4-7 → passes allowlist check but then fails with Unknown model: anthropic/claude-haiku-4-7 from the Anthropic API (model slug not recognised)
  • Only anthropic/claude-sonnet-4-6, deepseek/deepseek-chat, and google/gemini-2.5-flash are in the default allowlist

Impact

  • All lightweight crons that previously used haiku for cost efficiency are either broken or forced onto sonnet (~10x cost)
  • No automatic detection or remediation — users must manually identify and patch each cron
  • In our fleet: 7 Haderach crons affected, plus additional crons across other agents swept by fleet manager

Questions

  1. What is the correct Anthropic haiku model slug for v2026.5.4?
  2. Should claude-haiku-4-5claude-haiku-4-7 be an automatic migration on upgrade?
  3. Will the default agents.defaults.models config include a haiku entry in future releases?

Environment

  • OpenClaw v2026.5.4
  • macOS (arm64)
  • Anthropic provider
  • Multiple cron jobs with sessionTarget: isolated and payload.kind: agentTurn

extent analysis

TL;DR

Update the payload.model in cron jobs to a valid model slug allowed by the agents.defaults.models config, such as anthropic/claude-sonnet-4-6, until a haiku-tier model is added to the allowlist.

Guidance

  • Verify the current agents.defaults.models config to determine the list of allowed model slugs.
  • Check the Anthropic API documentation to find a valid haiku-tier model slug that can be used as a replacement for anthropic/claude-haiku-4-5.
  • Update the payload.model in affected cron jobs to a valid model slug, such as anthropic/claude-sonnet-4-6, to prevent immediate failure.
  • Monitor the consecutiveErrors count to ensure that the updated cron jobs are running successfully.

Example

No code snippet is provided as the issue is related to configuration and model slug updates.

Notes

The correct Anthropic haiku model slug for v2026.5.4 is not specified in the issue, and the anthropic/claude-haiku-4-7 slug is not recognized by the Anthropic API. The default agents.defaults.models config does not include a haiku-tier model, and there is no automatic migration path for claude-haiku-4-5 to a valid model slug.

Recommendation

Apply workaround: Update the payload.model in cron jobs to a valid model slug, such as anthropic/claude-sonnet-4-6, until a haiku-tier model is added to the allowlist. This will prevent immediate failure and allow cron jobs to run successfully, although it may incur higher costs due to the use of the sonnet model.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING