openclaw - 💡(How to fix) Fix Heartbeat rarely fires after upgrading to 2026.4.2 with MiniMax model [1 participants]

TL;DR

Check the sessions.json file for any signs of session key loss or corruption after upgrading to OpenClaw 2026.4.2, which might be related to pre-compaction memory operations affecting the heartbeat triggering mechanism.

Guidance

• Review the OpenClaw documentation and release notes for 2026.4.2 to see if there are any known issues or changes related to session management or heartbeat configuration.
• Investigate the possibility of session key loss or corruption by analyzing the sessions.json file and checking for any errors or inconsistencies.
• Consider setting an explicit heartbeat.model to see if it makes a difference in the heartbeat triggering behavior.
• Look into the related heartbeat bugs (#32983, #59996, #58484) to see if any of the fixes or workarounds might apply to this situation.

Example

No code snippet is provided as there is no clear indication of a specific code-related issue.

Notes

The issue seems to be related to the upgrade to OpenClaw 2026.4.2 and the use of the minimax/MiniMax-M2.7-highspeed model. The question about pre-compaction memory operations suggests that there might be some underlying issues with session management or memory handling.

Recommendation

Apply workaround: Try setting an explicit heartbeat.model and monitor the behavior to see if it resolves the issue, as this might help isolate the problem and provide more insight into the underlying cause.