openclaw - 💡(How to fix) Fix [Bug] Gateway cron tool returns empty list despite 43 jobs in jobs.json

Fix / Workaround

\n## Bug Description\n\nThe gateway's cron RPC tool (via cron tool in agent context) returns an empty jobs list {} despite 43 cron jobs existing in ~/.openclaw/cron/jobs.json.\n\n## Steps to Reproduce\n\n1. Have cron jobs stored in ~/.openclaw/cron/jobs.json (43 jobs confirmed)\n2. Query crons via the agent's cron tool using cron(action="list", includeDisabled=true) or cron(action="list")\n3. Result: {"jobs": [], "total": 0, ...} — empty list\n\n## Workaround\n\nopenclaw cron list --all via CLI correctly shows all 43 jobs (12 enabled, 31 disabled). The bug is specifically in the gateway's RPC handler for the cron tool.\n\n## Environment\n\n- macOS 26.5 (arm64)\n- OpenClaw v2026.5.19\n- Node v22.22.2\n- Gateway: LaunchAgent, ws://127.0.0.1:18789\n- Model: minimax-portal/MiniMax-M2.7\n\n## Investigation Notes\n\n- Cron jobs file: ~/.openclaw/cron/jobs.json — correctly structured with 43 jobs\n- Jobs state file: ~/.openclaw/cron/jobs-state.json — correctly structured\n- Gateway uses loadCronStore(resolveCronStorePath(params.cronStorePath)) from store-CToAht8n.js\n- Gateway config has no custom cron.store path override\n- CLI uses a different code path that works correctly\n- Gateway was restarted after the update — bug persists\n\n## Expected vs Actual\n\n| Method | Result |\n|--------|--------|\n| openclaw cron list --all (CLI) | ✅ Shows all 43 jobs |\n| cron(action="list", includeDisabled=true) (agent tool) | ❌ Returns empty {} |\n\nThis appears to be a regression introduced in today's update (v2026.5.19).\n