openclaw - 💡(How to fix) Fix [Bug]: Live Docs are ahead of release [3 comments, 4 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#48920Fetched 2026-04-08 00:51:01
View on GitHub
Comments
3
Participants
4
Timeline
5
Reactions
3
Author
Timeline (top)
commented ×3labeled ×2

Heartbeat IsolatedSessions is in the live docs but not in the latest version 2026.3.13

Root Cause

Heartbeat IsolatedSessions is in the live docs but not in the latest version 2026.3.13

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Summary

Heartbeat IsolatedSessions is in the live docs but not in the latest version 2026.3.13

Steps to reproduce

Add IsolatedSessions to your heartbeat config as per the docs:

https://docs.openclaw.ai/gateway/heartbeat#quick-start-beginner

You will get agents.defaults.heartbeat: Unrecognized key: "isolatedSession" errored,

Expected behavior

Live docs are kept in step with releases, show a version on the docs site

Actual behavior

Docs are ahead of latest version, adding this unsupported field took down my Telegram as config wouldn't parse

OpenClaw version

2026.3.13

Operating system

macOS

Install method

nom

Model

minimax

Provider / routing chain

minimax

Config file / key location

No response

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

Fix Plan

To resolve the issue, you need to remove the IsolatedSessions key from your Heartbeat configuration, as it is not supported in the latest version 2026.3.13.

Steps:

  • Open your Heartbeat configuration file.
  • Remove the IsolatedSessions key from the configuration.
  • Save the changes.

Example Code:

Before:

heartbeat:
  # ...
  IsolatedSessions: true

After:

heartbeat:
  # ...

Alternatively, you can comment out the IsolatedSessions key if you expect it to be supported in future versions:

heartbeat:
  # ...
  # IsolatedSessions: true

Verification

After removing the IsolatedSessions key, your Telegram should start working again, and the configuration should parse without errors. You can verify this by checking the logs for any error messages related to the IsolatedSessions key.

Extra Tips

Make sure to check the official documentation for the latest supported configuration options and version information to avoid similar issues in the future.

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

Live docs are kept in step with releases, show a version on the docs site

Still need to ship something?

×6

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

Back to top recommendations

TRENDING