When sending a message to WeCom times out, the error string "Timeout sending message to WeCom" is not recognized by _is_timeout_error(), causing it to fall through to the plain-text fallback. This results in the user receiving two identical messages — one prefixed with "(Response formatting failed, plain text:)".

TL;DR

Update the _is_timeout_error function to match error strings starting with "timeout" and reorder the error classification to check for timeouts before network errors.

Guidance

• Extend the _is_timeout_error function to include a check for error strings that start with "timeout" using the lowered.startswith("timeout") condition.
• Move the timeout check to execute before the is_network classification in the _send_with_retry method to prevent timeouts from being treated as retryable network errors.
• Verify the fix by triggering a timeout condition with the WeCom AI Bot adapter in WebSocket mode and observing that only one message is sent without the "(Response formatting failed, plain text:)" prefix.
• Review the gateway/platforms/base.py file to ensure the updated _is_timeout_error function and reordered error classification are correctly implemented.

Example

# _is_timeout_error
return (
    "timed out" in lowered
    or "readtimeout" in lowered
    or "writetimeout" in lowered
    or lowered.startswith("timeout")
)

# _send_with_retry — check timeout FIRST
if self._is_timeout_error(error_str):
    logger.warning("[%s] Send timed out — skipping retry and fallback to avoid duplicate delivery", self.name)
    return result

Notes

This fix assumes that the asyncio.TimeoutError caught by the WeCom adapter always raises an error string starting with "Timeout sending message to WeCom". If this is not the case, additional error handling may be necessary.

Recommendation

Apply the workaround by updating the _is_timeout_error function and reordering the error classification, as this directly addresses the identified root cause of the issue.