-
-
Notifications
You must be signed in to change notification settings - Fork 80.7k
[Bug]: Heartbeat scheduler silently fails to fire on 5.20 and all 5.x versions (regression from 4.23) #85871
Copy link
Copy link
Closed
Labels
P1High-priority user-facing bug, regression, or broken workflow.High-priority user-facing bug, regression, or broken workflow.bugSomething isn't workingSomething isn't workingclawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.ClawSweeper found an open linked pull request for this issue.clawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.ClawSweeper needs live local, crabbox, or manual validation to confirm this issue.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.Channel message delivery can be lost, duplicated, or misrouted.impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.Session, memory, transcript, context, or agent state can drift or corrupt.issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.Good issue quality with a plausible reproduction path needing some confirmation.regressionBehavior that previously worked and now failsBehavior that previously worked and now fails
Description
Metadata
Metadata
Assignees
Labels
P1High-priority user-facing bug, regression, or broken workflow.High-priority user-facing bug, regression, or broken workflow.bugSomething isn't workingSomething isn't workingclawsweeper:linked-pr-openClawSweeper found an open linked pull request for this issue.ClawSweeper found an open linked pull request for this issue.clawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.ClawSweeper needs live local, crabbox, or manual validation to confirm this issue.clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.impact:message-lossChannel message delivery can be lost, duplicated, or misrouted.Channel message delivery can be lost, duplicated, or misrouted.impact:session-stateSession, memory, transcript, context, or agent state can drift or corrupt.Session, memory, transcript, context, or agent state can drift or corrupt.issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.Good issue quality with a plausible reproduction path needing some confirmation.regressionBehavior that previously worked and now failsBehavior that previously worked and now fails
Type
Fields
Priority
None yet
Bug type
Regression (worked before, now fails)
Beta release blocker
No
Summary
The heartbeat scheduler does not fire on 2026.5.20 or any 5.x version. Confirmed broken on: 2026.4.24, 2026.4.27, 2026.4.29, and all 5.x versions tested up to and including 2026.5.20. No log output is produced — not even the heartbeat: started line that appears reliably on 2026.4.23. The scheduler appears to initialize silently and then do nothing.
Steps to reproduce
Steps to reproduce:
Install OpenClaw 2026.5.20
Run openclaw doctor --fix
Configure heartbeat in openclaw.json (e.g. every: 5m, target: none)
Start the gateway
Clear the log: > /tmp/openclaw/openclaw-.log
Wait 10+ minutes
Run grep -i heartbeat /tmp/openclaw/openclaw-.log
Expected behavior
Expected: Heartbeat fires every 5 minutes, logs heartbeat: started and routes to the target agent
Actual: Zero log output. No heartbeat activity whatsoever.
Confirmed working on: 2026.4.23 — heartbeat fires reliably, heartbeat: started appears in logs immediately, agent receives and processes the heartbeat prompt.
Environment:
Ubuntu 24.04
Node 24
Ollama local provider
Fresh install with doctor --fix run before starting gateway
Actual behavior
Heartbeat is not passing prompt to main agent session.
OpenClaw version
2026.5.20
Operating system
Ubuntu 24.04
Install method
npm install
Model
ollama/gemma4:26b
Provider / routing chain
ollama local
Additional provider/model setup details
Ollama local only - no cloud usage. Same results on other models. Not model provider issue. Heartbeat fires and works fine on 4.23 but not on any higher version. When manually triggered in CLI, result "OK" is returned, but it doesn't load the model and doesn't hit the main agent session.
Logs, screenshots, and evidence
Impact and severity
No response
Additional information
Additional related behavior: when attempting to create a new session in the main agent channel via the UI, the request instead generates an extra dashboard session. Messaging channel-initiated sessions work correctly. The dashboard sessions are functional but misrouted, and eventually disappear from the UI. This may share the same routing regression as the heartbeat issue.