openclaw - 💡(How to fix) Fix [Bug] Session content disappears from UI during Heartbeat execution [1 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#62929Fetched 2026-04-09 08:00:33
View on GitHub
Comments
0
Participants
1
Timeline
0
Reactions
0
Author
Participants

Code Example

# Gateway config
gateway.bind: lan (0.0.0.0)
gateway.controlUi.allowedOrigins: ["*"]

# Heartbeat config
heartbeat.interval: 120m

---

~/.openclaw/agents/main/sessions/
├── 001c4dc7-7ff7-460c-84ae-d351e4b6e19b.jsonl.reset.2026-04-07T10-39-39.817Z
├── 0756824c-659c-45cc-af50-db71bb25627a.jsonl.reset.2026-03-17T14-34-16.533Z
├── 08407870-de7c-4ef1-ba6e-0ce24bd9357b.jsonl
├── ... (multiple session files)
RAW_BUFFERClick to expand / collapse

OpenClaw Heartbeat UI Display Issue

Problem Description

During Heartbeat task execution, session content suddenly disappears from the UI interface.

Environment

  • OS: macOS 26.3 (Sonoma) - Mac mini M4 Pro (arm64)
  • OpenClaw Version: 2026.4.5
  • Node.js Version: v25.9.0
  • Installation: npm install -g openclaw
  • Migration Source: WSL2 (Ubuntu 22.04)

Issue Symptoms

  1. Heartbeat tasks are indeed executing (confirmed via cron logs)
  2. However, halfway through execution, session content disappears from the UI interface
  3. Session files themselves still exist (in ~/.openclaw/agents/main/sessions/)
  4. Issue persists after migrating from WSL2 to Mac mini

Configuration

# Gateway config
gateway.bind: lan (0.0.0.0)
gateway.controlUi.allowedOrigins: ["*"]

# Heartbeat config
heartbeat.interval: 120m

Session Directory Status

~/.openclaw/agents/main/sessions/
├── 001c4dc7-7ff7-460c-84ae-d351e4b6e19b.jsonl.reset.2026-04-07T10-39-39.817Z
├── 0756824c-659c-45cc-af50-db71bb25627a.jsonl.reset.2026-03-17T14-34-16.533Z
├── 08407870-de7c-4ef1-ba6e-0ce24bd9357b.jsonl
├── ... (multiple session files)

Cron Task Logs

From ~/.openclaw/cron/runs/ we can see tasks are executing:

  • Job ID: 84134237-c99e-41f1-a31f-b08be5104a64
  • Status: finished (ok)
  • But some tasks show "cron announce delivery failed"

Attempted Solutions

  1. Changed gateway.bind from loopback to lan
  2. Configured gateway.controlUi.allowedOrigins to ["*"]
  3. Restarted Gateway service

Possible Related Issues

  1. LCM (Lossless Context Management) plugin may cause UI display issues when compacting/summarizing sessions
  2. Path or permission issues after cross-platform migration
  3. Session files being locked or modified during heartbeat execution

Request for Help

Could the dev team help diagnose:

  1. Why does session content disappear from UI during heartbeat execution?
  2. How to view more detailed debug logs?
  3. Are there configuration options to control this behavior?

Attachments

  • Complete OpenClaw configuration file
  • Sample session files
  • Detailed log files

Additional Context

This issue significantly impacts the user experience as session history becomes inaccessible in the UI after heartbeat runs, even though the underlying data files remain intact. The UI becomes blank/empty, requiring manual intervention or session reset to restore visibility.

extent analysis

TL;DR

Check the LCM plugin configuration and session file permissions to resolve the UI display issue during Heartbeat task execution.

Guidance

  1. Verify LCM plugin configuration: Investigate if the LCM plugin is enabled and if its settings are causing the UI display issue during session compaction or summarization.
  2. Check session file permissions: Ensure that the session files in ~/.openclaw/agents/main/sessions/ have the correct permissions and are not being locked or modified during Heartbeat execution.
  3. Review cron task logs: Analyze the cron task logs in ~/.openclaw/cron/runs/ to identify any patterns or errors related to the "cron announce delivery failed" messages.
  4. Enable detailed debug logs: Investigate the OpenClaw configuration to enable more detailed debug logs, which may help diagnose the issue.
  5. Test with a minimal configuration: Try simplifying the OpenClaw configuration to isolate the issue and identify if any specific settings are causing the problem.

Example

No code snippet is provided as the issue is more related to configuration and permissions.

Notes

The issue may be related to the migration from WSL2 to Mac mini, and the LCM plugin or session file permissions might be the culprit. However, more information and debugging are needed to confirm the root cause.

Recommendation

Apply a workaround by disabling the LCM plugin or adjusting its configuration to prevent session compaction during Heartbeat execution, as this seems to be a likely cause of the UI display issue.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING