openclaw - 💡(How to fix) Fix Double reply on Slack/Telegram: same message processed on two lanes simultaneously (lane=main + lane=session:agent:main:...) [1 participants]

lane task error: lane=main durationMs=19446 error="FailoverError: LLM request timed out." lane task error: lane=session:agent:main:slack:direct:u09czr68x7c durationMs=19521 error="FailoverError: LLM request timed out."

TL;DR

Disable the lane=main processing for specific session types to prevent duplicate responses.

Guidance

• Investigate the OpenClaw configuration to see if there's an option to disable lane=main processing for specific session types, such as Slack and Telegram direct messages.
• Review the lane task error logs to understand the conditions under which the dual-lane dispatch occurs and identify potential patterns or triggers.
• Consider implementing deduplication logic to ensure that only one response is delivered to the channel, even if multiple lanes are processing the same inbound message.
• Examine the LiteLLM router fallbacks configuration to determine if there are any settings that can be adjusted to prevent the dual-lane dispatch.

Example

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

Notes

The dual-lane dispatch appears to be related to the primary model timeout/errors and fallback mechanism. The fix should focus on preventing the simultaneous processing of multiple lanes for the same inbound message.

Recommendation

Apply a workaround by disabling lane=main processing for specific session types, as this is likely to prevent the duplicate responses. This approach is recommended because it directly addresses the root cause of the issue and can be implemented without requiring significant changes to the underlying code or infrastructure.