openclaw - 💡(How to fix) Fix [Bug]: Cron job not triggering automatically (v2026.5.12)

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

Environment:

• OpenClaw Version: v2026.5.12 (f066dd2) • OS: Linux (WSL2) • Cron job ID: c5704ed9-ca61-4645-b62a-fd5beeafe5c2

Steps to reproduce

1. Create a cron job with schedule cron 0 11,16 * * 1-5 @ Asia/Hong_Kong
2. Wait for scheduled trigger time (e.g., 11:00 or 16:00)
3. Observe that no trigger occurs

Expected behavior

• Cron job should automatically trigger at scheduled times (11:00 and 16:00 on weekdays) • Run history should show new entries for each scheduled execution

Actual behavior

• Cron job does NOT trigger at scheduled times • No new entries appear in cron runs after the scheduled time passes • Manual trigger (cron run) works fine • cron status shows nextWakeAtMs correctly but never advances past it • The cron scheduler appears stuck — it never wakes up to execute the job

OpenClaw version

v2026.5.12 (f066dd2)

Operating system

windows 11

Install method

No response

Model

minimax/MiniMax-M2.5

Provider / routing chain

N/A

Additional provider/model setup details

What I've tried:

• Upgraded from v2026.5.7 to v2026.5.12 (per admin's suggestion that fix was queued for this release) • Bug persists in v2026.5.12 • Manual triggers work, but automatic scheduled triggers do not

Additional context:

• Related issue #81770 was previously reported but closed • Admin stated the fix would be in v2026.5.12, but it's not working

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

What I've tried:

• Upgraded from v2026.5.7 to v2026.5.12 (per admin's suggestion that fix was queued for this release) • Bug persists in v2026.5.12 • Manual triggers work, but automatic scheduled triggers do not

Additional context:

• Related issue #81770 was previously reported but closed • Admin stated the fix would be in v2026.5.12, but it's not working