openclaw - 💡(How to fix) Fix Session stuck in 'running' state after LLM timeout — abortedLastRun not updated [1 comments, 1 participants]

TL;DR

Update the session status to 'idle' and set abortedLastRun to true when an LLM run times out to recover the session.

Guidance

• Investigate the timeout handling mechanism in the LLM to ensure it correctly updates the session status and abortedLastRun flag.
• Verify that the session status is being updated correctly in other scenarios, such as successful LLM runs or manual aborts.
• Consider implementing a periodic cleanup task to identify and recover stuck sessions with a 'running' status.
• Review the OpenClaw documentation to see if there are any known issues or configuration options related to LLM timeout handling in version 2026.4.8.

Example

No explicit code example is provided, but the workaround involves updating the sessions.json file with the following changes:

{
  "status": "idle",
  "abortedLastRun": true
}

Notes

The provided workaround suggests that manually updating the session status and abortedLastRun flag can recover the session, but a more robust solution would involve fixing the underlying issue with the LLM timeout handling.

Recommendation

Apply a workaround to update the session status and abortedLastRun flag when an LLM run times out, as this is a more immediate solution to recover stuck sessions.