Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix [Bug] Heartbeat interrupts session tasks, switches model in WebUI, and Feishu channel becomes silent after tool errors [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#63484•Fetched 2026-04-09 07:53:15
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Author
ViyyyViyyy
Participants
ViyyyViyyy
Timeline (top)
labeled ×1

Observed multiple issues related to Heartbeat behavior and channel stability: (1) Heartbeat interrupts ongoing session tasks, (2) Heartbeat changes the active model during a session (visible in WebUI), (3) In Feishu channel, tool errors cause the assistant to become silent and stop responding.

Error Message

  • Let the tool fail (e.g., network error, invalid path)
  • Let the tool fail (e.g., network error, invalid path)
  • The silence after tool errors seems related to missing error-handling fallback in the agent loop

Root Cause

Observed multiple issues related to Heartbeat behavior and channel stability: (1) Heartbeat interrupts ongoing session tasks, (2) Heartbeat changes the active model during a session (visible in WebUI), (3) In Feishu channel, tool errors cause the assistant to become silent and stop responding.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Observed multiple issues related to Heartbeat behavior and channel stability: (1) Heartbeat interrupts ongoing session tasks, (2) Heartbeat changes the active model during a session (visible in WebUI), (3) In Feishu channel, tool errors cause the assistant to become silent and stop responding.

Steps to reproduce

  1. Start an OpenClaw session (via WebUI or Feishu channel)
  2. Let the agent perform a multi-step task (e.g., browser or exec workflow)
  3. Wait for Heartbeat to trigger during execution

Observed:

  • Current task is interrupted or stops progressing
  1. Continue interaction in WebUI

Observed:

  • The active model changes unexpectedly after Heartbeat
  1. In Feishu channel:
    • Trigger a tool call (e.g., browser/exec)
    • Let the tool fail (e.g., network error, invalid path)

Observed:

  • Assistant becomes silent (no further response)
  • Session appears stuck and requires manual user input to resume

Expected behavior

  1. Start an OpenClaw session (via WebUI or Feishu channel)
  2. Let the agent perform a multi-step task (e.g., browser or exec workflow)
  3. Wait for Heartbeat to trigger during execution

Observed:

  • Current task is interrupted or stops progressing
  1. Continue interaction in WebUI

Observed:

  • The active model changes unexpectedly after Heartbeat
  1. In Feishu channel:
    • Trigger a tool call (e.g., browser/exec)
    • Let the tool fail (e.g., network error, invalid path)

Observed:

  • Assistant becomes silent (no further response)
  • Session appears stuck and requires manual user input to resume

Actual behavior

  • Heartbeat interrupts execution of ongoing tasks
  • Active model changes unexpectedly during session (observed in WebUI)
  • Feishu channel becomes silent after tool errors and does not recover automatically

OpenClaw version

2026.04.01

Operating system

Ubuntu 24.04 (Docker container)

Install method

npm global

Model

gpt-5.4

Provider / routing chain

openclaw -> onehub -> gpt

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

  • The silence after tool errors seems related to missing error-handling fallback in the agent loop
  • Heartbeat may be interfering with session state or runtime context
  • The issue is reproducible and affects task continuity significantly

extent analysis

TL;DR

Implementing a more robust error-handling mechanism in the agent loop and reviewing Heartbeat's interaction with session state could mitigate the observed issues.

Guidance

  • Review the agent loop for missing error-handling fallbacks, particularly for tool errors, to prevent the assistant from becoming silent.
  • Investigate Heartbeat's behavior and its impact on session tasks and the active model to prevent interruptions and unexpected changes.
  • Consider implementing a mechanism to pause or resume session tasks during Heartbeat triggers to maintain task continuity.
  • Verify the session state and runtime context management to ensure that Heartbeat does not interfere with ongoing tasks.

Example

# Pseudo-example of error handling in the agent loop
try:
    # Tool call (e.g., browser/exec)
    tool_call()
except Exception as e:
    # Handle error and prevent silence
    handle_error(e)
    # Resume session or provide feedback
    resume_session()

Notes

The provided information suggests issues with Heartbeat and error handling, but specific implementation details are not available. The suggested steps are based on the observed behavior and may require adjustments based on the actual code and system architecture.

Recommendation

Apply workaround: Implementing a more robust error-handling mechanism and reviewing Heartbeat's interaction with session state can help mitigate the observed issues, as it directly addresses the reported problems with task interruptions, model changes, and silence after tool errors.

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

  1. Start an OpenClaw session (via WebUI or Feishu channel)
  2. Let the agent perform a multi-step task (e.g., browser or exec workflow)
  3. Wait for Heartbeat to trigger during execution

Observed:

  • Current task is interrupted or stops progressing
  1. Continue interaction in WebUI

Observed:

  • The active model changes unexpectedly after Heartbeat
  1. In Feishu channel:
    • Trigger a tool call (e.g., browser/exec)
    • Let the tool fail (e.g., network error, invalid path)

Observed:

  • Assistant becomes silent (no further response)
  • Session appears stuck and requires manual user input to resume
#memory optimization#batch processing#GPU compatibility#latency issue#model 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