openclaw - 💡(How to fix) Fix Telegram delivery: QUOTE_TEXT_INVALID not handled, drops messages instead of retrying without native quote [1 comments, 2 participants]

Telegram Bot API returns 400 Bad Request: QUOTE_TEXT_INVALID when a reply_parameters.quote field doesn't match the source message exactly (common after edit, deletion, or chunked-message reply). The current quote-error fallback only matches "quote not found", so QUOTE_TEXT_INVALID falls through and the entire reply is dropped.

TL;DR

Update the regular expression in delivery.send.ts to match QUOTE_TEXT_INVALID and trigger the quote-error fallback.

Guidance

• Review the proposed fix in extensions/telegram/src/bot/delivery.send.ts and apply the updated regular expression to match QUOTE_TEXT_INVALID.
• Verify that the fallback path is triggered correctly by checking the logs for successful retries without native quotes.
• Test the updated code with different scenarios, such as edited or chunked messages, to ensure the fix works as expected.
• Consider auditing other Bad Request: <CODE> strings from Telegram Bot API for similar fallback gaps.

Example

The proposed fix updates the regular expression to match QUOTE_TEXT_INVALID:

-const QUOTE_PARAM_RE = /\bquote not found\b/i;
+const QUOTE_PARAM_RE = /\bquote not found\b|QUOTE_TEXT_INVALID|quote text invalid/i;

Notes

The fix assumes that the handler already exists and works correctly, and only the matcher needs to be updated.

Recommendation

Apply the workaround by updating the regular expression in delivery.send.ts, as it is a targeted fix for the specific issue and does not introduce new dependencies or version changes.