openclaw - 💡(How to fix) Fix Bug: Heartbeat read tool called without path [1 comments, 2 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#57988Fetched 2026-04-08 01:55:15
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
0
Author
Participants
Timeline (top)
commented ×1

The heartbeat scheduler is calling the read tool without passing the path parameter correctly.

Error Message

Error Log

Root Cause

The heartbeat scheduler is calling the read tool without passing the path parameter correctly.

Code Example

[agent/embedded] read tool called without path: toolCallId=call_391c245501c54387b19a9c50 argsType=object
RAW_BUFFERClick to expand / collapse

Description

The heartbeat scheduler is calling the read tool without passing the path parameter correctly.

Error Log

[agent/embedded] read tool called without path: toolCallId=call_391c245501c54387b19a9c50 argsType=object

Details

-Version: OpenClaw 2026.3.28 (f9b1079) -Frequency: Every ~30 minutes (with heartbeat checks) -Source: Heartbeat scheduler trying to read HEARTBEAT.md automatically -Issue: The path parameter is not being passed correctly

Impact

-❌ Does not affect functionality -✅ Heartbeat works correctly -⚠️ Annoying log entries

Environment

-OS: Windows 10 (x64) -Node.js: v24.12.0 -Model: glm/glm-5 -Channel: webchat

Recommendation

Fix the path parameter passing in the heartbeat scheduler.

extent analysis

Fix Plan

To fix the issue, we need to modify the heartbeat scheduler to pass the path parameter correctly when calling the read tool. Here are the steps:

  • Identify the function in the heartbeat scheduler that calls the read tool.
  • Modify the function to pass the path parameter. For example:
// Before
readTool(args);

// After
const path = 'HEARTBEAT.md'; // or any other default path
readTool({ ...args, path });
  • Alternatively, if the path parameter is supposed to be dynamic, ensure that it is being generated or retrieved correctly before passing it to the read tool.

Verification

To verify that the fix worked:

  • Run the heartbeat scheduler and check the logs for the error message.
  • If the error message is no longer present, the fix was successful.
  • Additionally, verify that the heartbeat works correctly and that the read tool is able to read the file at the specified path.

Extra Tips

  • Make sure to test the fix in a non-production environment before deploying it to production.
  • Consider adding logging or monitoring to detect similar issues in the future.
  • Review the code to ensure that the path parameter is being handled correctly in all scenarios.

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