openclaw - 💡(How to fix) Fix Discord health monitor reports restart but active sessions are not recreated, making session-based checks look disconnected [1 participants]

TL;DR

The Discord sessions may not be properly recreated after a provider reconnect, causing sessions_list to not reflect the actual Discord connection health.

Guidance

• Review the channel provider reconnect logic to ensure it correctly recreates or updates Discord sessions after a restart.
• Verify the sessions_list implementation to confirm it accurately reflects the current state of Discord sessions.
• Consider updating the health-check recommendations to use a more reliable signal for Discord connection health, such as the openclaw status output.
• Investigate the possibility of updating to the latest available version (2026.4.21) to see if it resolves the issue.

Example

No specific code snippet can be provided without more context, but the reconnect logic and sessions_list implementation should be reviewed for potential issues.

Notes

The exact cause of the issue is unclear, and more investigation is needed to determine the root cause. The suggested direction is to clarify the lifecycle contract between channel provider reconnects and session materialization.

Recommendation

Apply workaround: Update health-check recommendations to use a more reliable signal for Discord connection health, such as the openclaw status output, until the root cause of the issue can be determined and fixed. This is because the current implementation of sessions_list may not accurately reflect the Discord connection health after a provider reconnect.