openclaw - 💡(How to fix) Fix Server-side timeout for sessions stuck in 'processing' state [1 comments, 2 participants]

TL;DR

Implementing a configurable timeout for sessions in the 'processing' state can help prevent them from remaining stuck indefinitely.

Guidance

• Introduce a configurable timeout (e.g., default 2 hours) for sessions in the 'processing' state with queueDepth=0 and no recent log activity.
• Modify the stuck session detector to auto-fail sessions that exceed the configured timeout.
• Surface auto-failed sessions in the 'openclaw status --deep' output for easier identification and handling.
• Consider testing the proposed solution in a controlled environment to ensure it effectively resolves the issue without introducing unintended consequences.

Example

No explicit code example is provided due to the lack of specific implementation details in the issue.

Notes

The proposed solution assumes that the addition of a configurable timeout and auto-failure mechanism will not interfere with existing functionality or introduce new issues. Further testing and review are necessary to confirm the effectiveness and safety of this approach.

Recommendation

Apply workaround: Implementing a configurable timeout for sessions in the 'processing' state, as it directly addresses the issue of sessions becoming stuck indefinitely due to the agent_end hook failing or a subagent's announce never arriving.