Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug]: openclaw cron list closes with 1000 while cron scheduler is running (2026.3.13) [2 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#50964•Fetched 2026-04-08 01:06:12
View on GitHub
Comments
2
Participants
3
Timeline
4
Reactions
1
Author
bloommediacorporation-labbloommediacorporation-lab
Participants
ArtyomkunArtyomkunastroclawastroclawbloommediacorporation-labbloommediacorporation-lab
Timeline (top)
commented ×2labeled ×2
  • Version: OpenClaw 2026.3.13
  • Host: Linux VPS, root user, systemd user service
  • openclaw gateway status => RPC probe: ok, listener active on 127.0.0.1:18789
  • openclaw cron list => gateway closed (1000 normal closure): no close reason Cron is actually active: /root/.openclaw/cron/jobs.json contains 6 jobs logs contain cron: started with jobs: 6 run logs exist under /root/.openclaw/cron/runs/*.jsonl

Root Cause

  • Version: OpenClaw 2026.3.13
  • Host: Linux VPS, root user, systemd user service
  • openclaw gateway status => RPC probe: ok, listener active on 127.0.0.1:18789
  • openclaw cron list => gateway closed (1000 normal closure): no close reason Cron is actually active: /root/.openclaw/cron/jobs.json contains 6 jobs logs contain cron: started with jobs: 6 run logs exist under /root/.openclaw/cron/runs/*.jsonl
RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Summary

  • Version: OpenClaw 2026.3.13
  • Host: Linux VPS, root user, systemd user service
  • openclaw gateway status => RPC probe: ok, listener active on 127.0.0.1:18789
  • openclaw cron list => gateway closed (1000 normal closure): no close reason Cron is actually active: /root/.openclaw/cron/jobs.json contains 6 jobs logs contain cron: started with jobs: 6 run logs exist under /root/.openclaw/cron/runs/*.jsonl

Steps to reproduce

Install/OpenClaw version: 2026.3.13 on Linux VPS (root), gateway as systemd user service. Set gateway local loopback: gateway.mode=local gateway.bind=loopback gateway.auth.mode=token (am testat și cu none, comportament similar pe cron list) Start/restart gateway: openclaw gateway restart Verify gateway health: openclaw gateway status Observed: Runtime: running, RPC probe: ok, Listening: 127.0.0.1:18789 Run: openclaw cron list Observe failure: gateway closed (1000 normal closure): no close reason Verify cron scheduler is actually active: /root/.openclaw/cron/jobs.json exists and contains 6 jobs log includes cron: started with jobs: 6 run log exists under /root/.openclaw/cron/runs/*.jsonl

Expected behavior: openclaw cron list should return existing jobs. Actual behavior: command fails with close code 1000, even though scheduler is running and jobs exist.

Expected behavior

openclaw cron list should successfully return all persisted cron jobs from the active store (/root/.openclaw/cron/jobs.json) when the gateway is running and reachable (RPC probe: ok), without closing the WebSocket connection.

Actual behavior

openclaw cron list fails with: gateway closed (1000 normal closure): no close reason even though openclaw gateway status reports Runtime: running, RPC probe: ok, and cron is active (cron: started, jobs present in /root/.openclaw/cron/jobs.json).

OpenClaw version

2026.3.13

Operating system

Ubuntu 24.04

Install method

No response

Model

nvidia/minimaxai/minimax-m2.5

Provider / routing chain

openclaw -> NVIDIA NIM -> minimax-m2.5

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

Fix Plan

The fix involves updating the openclaw configuration to properly handle WebSocket connections for the cron list command.

  • Update the gateway.mode to remote instead of local to allow for proper WebSocket handling:

gateway.mode=remote

* Ensure that the `gateway.bind` is set to `0.0.0.0` to listen on all available network interfaces:
  ```bash
gateway.bind=0.0.0.0
  • Restart the openclaw gateway service to apply the changes:

openclaw gateway restart

* Verify that the `cron list` command works as expected:
  ```bash
openclaw cron list

Verification

To verify that the fix worked, check that the openclaw cron list command returns the existing jobs without closing the WebSocket connection. You can also check the openclaw logs for any error messages related to WebSocket connections.

Extra Tips

  • Make sure to update the openclaw configuration file with the correct syntax and formatting.
  • If you are using a firewall, ensure that it allows incoming connections on the port specified in the gateway.bind configuration.
  • You can also try setting the gateway.auth.mode to none to disable authentication and see if it makes a difference.

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…

FAQ

Expected behavior

openclaw cron list should successfully return all persisted cron jobs from the active store (/root/.openclaw/cron/jobs.json) when the gateway is running and reachable (RPC probe: ok), without closing the WebSocket connection.

#api#ssr#installation#tensor shape#autograd error#conversation history#tool integration#LLM response#prompt template#agent execution

Still need to ship something?

×6

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

Back to top recommendations

TRENDING