fix(telegram): fall back to text when voice messages forbidden #1725
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
377d3ba to
ae84ea8
Compare
When TTS auto mode is enabled, slash commands like /status would fail silently because sendVoice was rejected with VOICE_MESSAGES_FORBIDDEN. The entire reply would fail without any text being sent. This adds error handling to catch VOICE_MESSAGES_FORBIDDEN specifically and fall back to sending the text content as a regular message instead of failing completely. Co-Authored-By: Claude Opus 4.5 <[email protected]>
ae84ea8 to
58f3681
Compare
Contributor
|
Landed via temp rebase onto main.
Thanks @$contrib! |
steipete
added a commit
to orlyjamie/clawdbot
that referenced
this pull request
Jan 25, 2026
…law#1725) * fix(telegram): fall back to text when voice messages forbidden When TTS auto mode is enabled, slash commands like /status would fail silently because sendVoice was rejected with VOICE_MESSAGES_FORBIDDEN. The entire reply would fail without any text being sent. This adds error handling to catch VOICE_MESSAGES_FORBIDDEN specifically and fall back to sending the text content as a regular message instead of failing completely. Co-Authored-By: Claude Opus 4.5 <[email protected]> * fix: handle telegram voice fallback errors (openclaw#1725) (thanks @foeken) --------- Co-authored-by: Echo <[email protected]> Co-authored-by: Claude Opus 4.5 <[email protected]> Co-authored-by: Peter Steinberger <[email protected]>
mcinteerj
pushed a commit
to mcinteerj/moltbot
that referenced
this pull request
Jan 25, 2026
…law#1725) * fix(telegram): fall back to text when voice messages forbidden When TTS auto mode is enabled, slash commands like /status would fail silently because sendVoice was rejected with VOICE_MESSAGES_FORBIDDEN. The entire reply would fail without any text being sent. This adds error handling to catch VOICE_MESSAGES_FORBIDDEN specifically and fall back to sending the text content as a regular message instead of failing completely. Co-Authored-By: Claude Opus 4.5 <[email protected]> * fix: handle telegram voice fallback errors (openclaw#1725) (thanks @foeken) --------- Co-authored-by: Echo <[email protected]> Co-authored-by: Claude Opus 4.5 <[email protected]> Co-authored-by: Peter Steinberger <[email protected]>
rodrigouroz
pushed a commit
to rodrigouroz/moltbot
that referenced
this pull request
Jan 26, 2026
…law#1725) * fix(telegram): fall back to text when voice messages forbidden When TTS auto mode is enabled, slash commands like /status would fail silently because sendVoice was rejected with VOICE_MESSAGES_FORBIDDEN. The entire reply would fail without any text being sent. This adds error handling to catch VOICE_MESSAGES_FORBIDDEN specifically and fall back to sending the text content as a regular message instead of failing completely. Co-Authored-By: Claude Opus 4.5 <[email protected]> * fix: handle telegram voice fallback errors (openclaw#1725) (thanks @foeken) --------- Co-authored-by: Echo <[email protected]> Co-authored-by: Claude Opus 4.5 <[email protected]> Co-authored-by: Peter Steinberger <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
/statuswould fail silently becausesendVoicewas rejected withVOICE_MESSAGES_FORBIDDENVOICE_MESSAGES_FORBIDDENspecifically and fall back to sending the text content as a regular messageProblem
When a Telegram chat/user has voice messages disabled (privacy setting or bot restriction), any reply with TTS enabled would completely fail:
This meant
/status,/help, and other slash commands appeared broken when TTS auto mode was enabled.Why does VOICE_MESSAGES_FORBIDDEN happen?
This is a Telegram Premium privacy feature. Premium users can block voice/video messages in Settings > Privacy and Security > Voice Messages. They can choose who's allowed to send them voice messages (everyone, contacts only, nobody, etc.).
If the recipient has this restriction enabled and the bot isn't on their allowed list, Telegram rejects the
sendVoicecall with this error.Users experiencing this can either:
messages.tts.auto: "off")Solution
Added try-catch around
sendVoicethat:VOICE_MESSAGES_FORBIDDENerrors specificallysendMessageinsteadTest plan
🤖 Generated with Claude Code