Bug

When a user withdraws/deletes a message while the agent is still processing, the reply is silently lost. The agent generates a response but it never reaches the user.

Observed behavior (from logs)

1. User sends messages (file + text) to Feishu bot
2. User withdraws the message while agent is processing
3. Typing indicator retries ~25 times against the deleted message (code 231003: The message is not found), no backoff or early stop
4. Agent finishes and attempts to reply → fails with code 230011: The message was withdrawn
5. Reply is silently discarded — user sees nothing

Expected behavior

1. When reply target message returns 230011 (withdrawn) or 231003 (not found), fall back to sending a direct message (no reply-to) instead of discarding
2. Typing indicator should stop retrying on 231003/230011 instead of looping every 6s

Environment

• @openclaw/feishu 2026.2.23
• OpenClaw 2026.2.23

Logs

01:10:53 [feishu] failed to add typing indicator: AxiosError: Request failed with status code 400
  → code: 231003, msg: "The message is not found, maybe not exist or deleted"
  (repeated ~25 times at 6s intervals)

01:13:03 [feishu] block reply failed: AxiosError: Request failed with status code 400
  → code: 230011, msg: "The message was withdrawn."

01:13:30 [feishu] block reply failed (same 230011)