openclaw - 💡(How to fix) Fix Session history blocks startup for ~20 minutes on fresh install [2 comments, 2 participants]

TL;DR

Deferring or disabling the startup prune process may help resolve the delayed gateway startup issue.

Guidance

• Investigate the session maintenance policy introduced in version 4.20 (PR #69404) and its impact on the session store during startup.
• Consider deferring or disabling the startup prune process for debugging purposes to determine if it's the root cause of the delay.
• Review the sequencing of session history loading and store initialization to ensure that chat.history is not attempting to read from the store before it's fully ready.
• Verify that the issue is specific to the local loopback gateway setup or if it's also present in other environments.

Example

No code snippet is provided as the issue does not contain sufficient information to create a specific example.

Notes

The issue may be specific to the combination of OpenClaw version 2026.4.21 and the local loopback gateway setup. Further testing and debugging are needed to confirm the root cause and determine the best solution.

Recommendation

Apply workaround: Defer or disable the startup prune process to see if it resolves the issue, as this is the most likely cause based on the provided information.