openclaw - 💡(How to fix) Fix bug: failed/errored ACP sessions not evicted from concurrent session count [1 participants]

1. Error: ACP max concurrent sessions reached (3/3) Failed/errored sessions should be automatically evicted from the concurrent session count. Any terminal state (done, failed, error) should decrement the count.

TL;DR

Decrement the in-memory concurrent session count when an ACP session fails to prevent failed sessions from counting against the maximum concurrent sessions limit.

Guidance

• Review the session management logic to ensure that failed sessions are properly removed from the in-memory count.
• Consider implementing a mechanism to automatically evict failed sessions from the concurrent session count, such as a periodic cleanup task.
• Verify that the sessions.json file is properly updated to reflect the terminal state of failed sessions.
• Investigate the possibility of adding a retry mechanism or a timeout for failed sessions to prevent them from permanently occupying a session slot.

Example

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

Notes

The provided guidance assumes that the issue is related to the session management logic and the in-memory count of concurrent sessions. Further investigation may be required to determine the root cause of the issue.

Recommendation

Apply a workaround, such as manually clearing sessions.json or implementing a periodic cleanup task, until a permanent fix can be developed and deployed. This is because the current behavior can lead to permanent exhaustion of the session pool, requiring manual operator intervention to recover.