openclaw - 💡(How to fix) Fix [Bug]: cron jobs once again failing with model idle timeout in 2026.5.7 [1 comments, 2 participants]

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

I am on MiniMax M2.7 Isolated cron sessions were failing for me with error The model did not produce a response before the model idle timeout until about 2026.4.23 where the issue was resolved for a while.

Now I upgraded to 2026.5.7 and the same issue is back, cron sessions failing with:

{
  "ts": 1778335337761,
  "source": "tool",
  "severity": "error",
  "message": "The model did not produce a response before the model idle timeout. Please try again, or increase `models.providers.<id>.timeoutSeconds` for slow local or self-hosted providers."
}

Tried explicitly setting model timeout to 600 but no effect.

I have two types of cron jobs, either should take just a few seconds to run but but both timeout similarly:

1. send a simple text reminder, no tool use
2. use a CLI to retrieve and display some blogs

Requesting execution of exact same steps are in the cron jobs via main session succeeds promptly.

AI analysis:

Ran it directly via spawn — completed successfully in 21 seconds, got full output. No stall. So the model and API are fine. The issue is specifically with cron-triggered isolated sessions — they stall at 40-60 tokens, but a manually spawned subagent completes cleanly.

Steps to reproduce

1. Start with OpenClaw 2026.5.7 and MiniMax M2.7 (not sure if model type matters, same model worked fine for 2026.4.23)
2. Schedule an isolated cron job

Expected behavior

Cron job executes and runs successfully in under a minute

Actual behavior

At time of execution an error is reported in Telegram Cron job "Job Name" failed: cron: job execution timed out

OpenClaw version

2026.5.7

Operating system

Ubuntu 24.04

Install method

npm global

Model

MiniMax M2.7

Provider / routing chain

openclaw -> gateway -> model

Additional provider/model setup details

No fallback model

Logs, screenshots, and evidence

Impact and severity

Affected: just me as a sole user Severity: annoying, personal crons Frequency: any time cron should trigger Consequence: negligible

Additional information

No response