fix(telegram): improve error messages for 403 bot not member errors by w-sss · Pull Request #53635 · openclaw/openclaw

w-sss · 2026-03-24T11:06:49Z

Restored PR #48650

greptile-apps · 2026-03-24T11:08:52Z

Greptile Summary

This PR improves wrapTelegramChatNotFoundError in send.ts to surface actionable error messages when the bot encounters 403 Forbidden responses indicating it is not a member of a chat or has been blocked, rather than propagating the raw Telegram API error.

The new 403 branch is correctly placed before the existing CHAT_NOT_FOUND_RE (400) check and follows the same message-formatting pattern as the existing handler.
Two minor gaps: the regex doesn't cover bot was kicked from the … chat (another common 403 scenario), and there are no new test cases to accompany the new branch (the existing CHAT_NOT_FOUND_RE path has dedicated tests in send.test.ts).

Confidence Score: 4/5

Safe to merge; the change is a net improvement with no regressions and only minor gaps in coverage.
The implementation is correct and well-scoped. Ordering of the new branch is right, the error format is consistent with the existing handler, and no existing tests are broken. Two non-blocking P2 items remain: the "bot was kicked" 403 variant is not covered by the regex, and there are no new unit tests for the added path.
extensions/telegram/src/send.ts — review the regex coverage and consider adding tests in send.test.ts

Prompt To Fix All With AI

This is a comment left during a code review.
Path: extensions/telegram/src/send.ts
Line: 497

Comment:
**"bot was kicked" case not covered**

The regex handles `bot.*not.*member` and `bot.*blocked`, but Telegram also emits `403: Forbidden: bot was kicked from the group chat` (and supergroup/channel variants). These errors currently fall through to `return err` (raw, cryptic error), just as before this PR.

Consider extending the alternation to cover kicks as well:

```suggestion
  if (/403.*(bot.*not.*member|bot.*blocked|bot.*kicked)/i.test(errorMsg)) {
```

And update the user-facing message to mention removal/kicking alongside "not a member".

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: extensions/telegram/src/send.ts
Line: 497-505

Comment:
**No test coverage for new 403 path**

The existing `400: Bad Request: chat not found` branch is covered by the `"wraps chat-not-found with actionable context"` test suite in `send.test.ts` (line 1814). The new `403` branch has no corresponding test cases.

Adding a test that mocks a rejection with e.g. `new Error("403: Forbidden: bot is not a member of the channel chat")` and asserts that the thrown message contains the actionable hint would prevent future regressions here.

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "fix(telegram): correct regex alternation..." | Re-trigger Greptile}

greptile-apps · 2026-03-24T11:08:56Z

+  const errorMsg = formatErrorMessage(err);
+
+  // Check for 403 "bot is not a member" or "bot was blocked" errors
+  if (/403.*(bot.*not.*member|bot.*blocked)/i.test(errorMsg)) {


"bot was kicked" case not covered

The regex handles bot.*not.*member and bot.*blocked, but Telegram also emits 403: Forbidden: bot was kicked from the group chat (and supergroup/channel variants). These errors currently fall through to return err (raw, cryptic error), just as before this PR.

Consider extending the alternation to cover kicks as well:

Suggested change

if (/403.*(bot.*not.*member|bot.*blocked)/i.test(errorMsg)) {

if (/403.*(bot.*not.*member|bot.*blocked|bot.*kicked)/i.test(errorMsg)) {

And update the user-facing message to mention removal/kicking alongside "not a member".

Prompt To Fix With AI

This is a comment left during a code review. Path: extensions/telegram/src/send.ts Line: 497 Comment: **"bot was kicked" case not covered** The regex handles `bot.*not.*member` and `bot.*blocked`, but Telegram also emits `403: Forbidden: bot was kicked from the group chat` (and supergroup/channel variants). These errors currently fall through to `return err` (raw, cryptic error), just as before this PR. Consider extending the alternation to cover kicks as well: ```suggestion if (/403.*(bot.*not.*member|bot.*blocked|bot.*kicked)/i.test(errorMsg)) { ``` And update the user-facing message to mention removal/kicking alongside "not a member". How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2026-03-24T11:08:57Z

+  if (/403.*(bot.*not.*member|bot.*blocked)/i.test(errorMsg)) {
+    return new Error(
+      [
+        `Telegram send failed: bot is not a member of the chat or was blocked (chat_id=${params.chatId}).`,
+        "Fix: Add the bot to the channel/group, or ensure it has not been removed/blocked by the user.",
+        `Input was: ${JSON.stringify(params.input)}.`,
+      ].join(" "),
+    );
+  }


No test coverage for new 403 path

The existing 400: Bad Request: chat not found branch is covered by the "wraps chat-not-found with actionable context" test suite in send.test.ts (line 1814). The new 403 branch has no corresponding test cases.

Adding a test that mocks a rejection with e.g. new Error("403: Forbidden: bot is not a member of the channel chat") and asserts that the thrown message contains the actionable hint would prevent future regressions here.

Prompt To Fix With AI

This is a comment left during a code review. Path: extensions/telegram/src/send.ts Line: 497-505 Comment: **No test coverage for new 403 path** The existing `400: Bad Request: chat not found` branch is covered by the `"wraps chat-not-found with actionable context"` test suite in `send.test.ts` (line 1814). The new `403` branch has no corresponding test cases. Adding a test that mocks a rejection with e.g. `new Error("403: Forbidden: bot is not a member of the channel chat")` and asserts that the thrown message contains the actionable hint would prevent future regressions here. How can I resolve this? If you propose a fix, please make it concise.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4fa7211177

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector · 2026-03-24T11:12:30Z

+        `Telegram send failed: bot is not a member of the chat or was blocked (chat_id=${params.chatId}).`,
+        "Fix: Add the bot to the channel/group, or ensure it has not been removed/blocked by the user.",


Preserve permanent-error tokens in wrapped 403 failures

This replacement message drops Telegram’s original phrases (for example, bot was blocked by the user / forbidden: bot was kicked) that downstream classifiers use to mark delivery errors as permanent, so these 403 membership/blocking failures can now be misclassified as retryable. I checked src/infra/outbound/delivery-queue.ts and src/agents/subagent-announce.ts, where permanent matching relies on those original substrings; with this new text, blocked/not-member errors can be retried unnecessarily until retry limits instead of being handled as terminal failures.

Useful? React with 👍 / 👎.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 89d816e3c6

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector · 2026-03-24T14:11:34Z

+        `Telegram send failed: bot is not a member of the chat, was blocked, or was kicked (chat_id=${params.chatId}).`,
+        "Fix: Add the bot to the channel/group, or ensure it has not been removed/blocked/kicked by the user.",


Preserve Telegram forbidden substrings in wrapped errors

When a Telegram send fails with a 403 blocked/kicked/not-member error, this wrapper replaces the original provider text with a new message that no longer contains the tokens our permanent-error classifiers match (for example bot was blocked by the user / forbidden: bot was kicked). I checked src/infra/outbound/delivery-queue-recovery.ts, src/agents/subagent-announce.ts, and src/cron/isolated-agent/delivery-dispatch.ts; each uses those substrings to avoid retries, so these failures can now be misclassified as retryable and churn through retry loops instead of being treated as terminal.

Useful? React with 👍 / 👎.

- Detect 403 'bot is not a member' errors specifically - Provide actionable guidance for users to fix the issue - Fixes openclaw#48273 where outbound sendMessage fails with 403 Root cause: When a Telegram bot tries to send a message to a channel/group it's not a member of, the API returns 403 'bot is not a member of the channel chat'. The error message was not clear about how to fix this. Fix: 1. Detect 403 errors in wrapTelegramChatNotFoundError 2. Provide clear error message explaining the issue 3. Suggest adding the bot to the channel/group

- Group alternatives correctly: /403.*(bot.*not.*member|bot was blocked)/i - Require 403 for both alternatives (previously bot.*blocked matched any error) - Update error message to cover both scenarios - Fixes Greptile review feedback

- Fix: /403.*(bot.*not.*member|bot was blocked)/ → /403.*(bot.*not.*member|bot.*blocked)/ - Ensures 403 requirement applies to both alternatives - Fixes Greptile review comment on PR openclaw#48650

@w-sss

… (thanks @w-sss)

obviyus · 2026-03-25T05:29:46Z

Landed on main.

Landed source commit: f16e2b7
Merge commit: 247f821

Thanks @w-sss.

@w-sss

… (thanks @w-sss) * fix(telegram): improve error messages for 403 bot not member errors - Detect 403 'bot is not a member' errors specifically - Provide actionable guidance for users to fix the issue - Fixes openclaw#48273 where outbound sendMessage fails with 403 Root cause: When a Telegram bot tries to send a message to a channel/group it's not a member of, the API returns 403 'bot is not a member of the channel chat'. The error message was not clear about how to fix this. Fix: 1. Detect 403 errors in wrapTelegramChatNotFoundError 2. Provide clear error message explaining the issue 3. Suggest adding the bot to the channel/group * fix(telegram): fix regex precedence for 403 error detection - Group alternatives correctly: /403.*(bot.*not.*member|bot was blocked)/i - Require 403 for both alternatives (previously bot.*blocked matched any error) - Update error message to cover both scenarios - Fixes Greptile review feedback * fix(telegram): correct regex alternation precedence for 403 errors - Fix: /403.*(bot.*not.*member|bot was blocked)/ → /403.*(bot.*not.*member|bot.*blocked)/ - Ensures 403 requirement applies to both alternatives - Fixes Greptile review comment on PR openclaw#48650 * fix(telegram): add 'bot was kicked' to 403 error regex and message * fix(telegram): preserve membership delivery errors * fix: improve Telegram 403 membership delivery errors (openclaw#53635) (thanks @w-sss) --------- Co-authored-by: Ayaan Zaidi <hi@obviy.us>

@w-sss

… (thanks @w-sss) * fix(telegram): improve error messages for 403 bot not member errors - Detect 403 'bot is not a member' errors specifically - Provide actionable guidance for users to fix the issue - Fixes openclaw#48273 where outbound sendMessage fails with 403 Root cause: When a Telegram bot tries to send a message to a channel/group it's not a member of, the API returns 403 'bot is not a member of the channel chat'. The error message was not clear about how to fix this. Fix: 1. Detect 403 errors in wrapTelegramChatNotFoundError 2. Provide clear error message explaining the issue 3. Suggest adding the bot to the channel/group * fix(telegram): fix regex precedence for 403 error detection - Group alternatives correctly: /403.*(bot.*not.*member|bot was blocked)/i - Require 403 for both alternatives (previously bot.*blocked matched any error) - Update error message to cover both scenarios - Fixes Greptile review feedback * fix(telegram): correct regex alternation precedence for 403 errors - Fix: /403.*(bot.*not.*member|bot was blocked)/ → /403.*(bot.*not.*member|bot.*blocked)/ - Ensures 403 requirement applies to both alternatives - Fixes Greptile review comment on PR openclaw#48650 * fix(telegram): add 'bot was kicked' to 403 error regex and message * fix(telegram): preserve membership delivery errors * fix: improve Telegram 403 membership delivery errors (openclaw#53635) (thanks @w-sss) --------- Co-authored-by: Ayaan Zaidi <hi@obviy.us>

@w-sss

… (thanks @w-sss) * fix(telegram): improve error messages for 403 bot not member errors - Detect 403 'bot is not a member' errors specifically - Provide actionable guidance for users to fix the issue - Fixes openclaw#48273 where outbound sendMessage fails with 403 Root cause: When a Telegram bot tries to send a message to a channel/group it's not a member of, the API returns 403 'bot is not a member of the channel chat'. The error message was not clear about how to fix this. Fix: 1. Detect 403 errors in wrapTelegramChatNotFoundError 2. Provide clear error message explaining the issue 3. Suggest adding the bot to the channel/group * fix(telegram): fix regex precedence for 403 error detection - Group alternatives correctly: /403.*(bot.*not.*member|bot was blocked)/i - Require 403 for both alternatives (previously bot.*blocked matched any error) - Update error message to cover both scenarios - Fixes Greptile review feedback * fix(telegram): correct regex alternation precedence for 403 errors - Fix: /403.*(bot.*not.*member|bot was blocked)/ → /403.*(bot.*not.*member|bot.*blocked)/ - Ensures 403 requirement applies to both alternatives - Fixes Greptile review comment on PR openclaw#48650 * fix(telegram): add 'bot was kicked' to 403 error regex and message * fix(telegram): preserve membership delivery errors * fix: improve Telegram 403 membership delivery errors (openclaw#53635) (thanks @w-sss) --------- Co-authored-by: Ayaan Zaidi <hi@obviy.us>

@w-sss

… (thanks @w-sss) * fix(telegram): improve error messages for 403 bot not member errors - Detect 403 'bot is not a member' errors specifically - Provide actionable guidance for users to fix the issue - Fixes openclaw#48273 where outbound sendMessage fails with 403 Root cause: When a Telegram bot tries to send a message to a channel/group it's not a member of, the API returns 403 'bot is not a member of the channel chat'. The error message was not clear about how to fix this. Fix: 1. Detect 403 errors in wrapTelegramChatNotFoundError 2. Provide clear error message explaining the issue 3. Suggest adding the bot to the channel/group * fix(telegram): fix regex precedence for 403 error detection - Group alternatives correctly: /403.*(bot.*not.*member|bot was blocked)/i - Require 403 for both alternatives (previously bot.*blocked matched any error) - Update error message to cover both scenarios - Fixes Greptile review feedback * fix(telegram): correct regex alternation precedence for 403 errors - Fix: /403.*(bot.*not.*member|bot was blocked)/ → /403.*(bot.*not.*member|bot.*blocked)/ - Ensures 403 requirement applies to both alternatives - Fixes Greptile review comment on PR openclaw#48650 * fix(telegram): add 'bot was kicked' to 403 error regex and message * fix(telegram): preserve membership delivery errors * fix: improve Telegram 403 membership delivery errors (openclaw#53635) (thanks @w-sss) --------- Co-authored-by: Ayaan Zaidi <hi@obviy.us>

@w-sss

… (thanks @w-sss) * fix(telegram): improve error messages for 403 bot not member errors - Detect 403 'bot is not a member' errors specifically - Provide actionable guidance for users to fix the issue - Fixes openclaw#48273 where outbound sendMessage fails with 403 Root cause: When a Telegram bot tries to send a message to a channel/group it's not a member of, the API returns 403 'bot is not a member of the channel chat'. The error message was not clear about how to fix this. Fix: 1. Detect 403 errors in wrapTelegramChatNotFoundError 2. Provide clear error message explaining the issue 3. Suggest adding the bot to the channel/group * fix(telegram): fix regex precedence for 403 error detection - Group alternatives correctly: /403.*(bot.*not.*member|bot was blocked)/i - Require 403 for both alternatives (previously bot.*blocked matched any error) - Update error message to cover both scenarios - Fixes Greptile review feedback * fix(telegram): correct regex alternation precedence for 403 errors - Fix: /403.*(bot.*not.*member|bot was blocked)/ → /403.*(bot.*not.*member|bot.*blocked)/ - Ensures 403 requirement applies to both alternatives - Fixes Greptile review comment on PR openclaw#48650 * fix(telegram): add 'bot was kicked' to 403 error regex and message * fix(telegram): preserve membership delivery errors * fix: improve Telegram 403 membership delivery errors (openclaw#53635) (thanks @w-sss) --------- Co-authored-by: Ayaan Zaidi <hi@obviy.us>

@w-sss

… (thanks @w-sss) * fix(telegram): improve error messages for 403 bot not member errors - Detect 403 'bot is not a member' errors specifically - Provide actionable guidance for users to fix the issue - Fixes openclaw#48273 where outbound sendMessage fails with 403 Root cause: When a Telegram bot tries to send a message to a channel/group it's not a member of, the API returns 403 'bot is not a member of the channel chat'. The error message was not clear about how to fix this. Fix: 1. Detect 403 errors in wrapTelegramChatNotFoundError 2. Provide clear error message explaining the issue 3. Suggest adding the bot to the channel/group * fix(telegram): fix regex precedence for 403 error detection - Group alternatives correctly: /403.*(bot.*not.*member|bot was blocked)/i - Require 403 for both alternatives (previously bot.*blocked matched any error) - Update error message to cover both scenarios - Fixes Greptile review feedback * fix(telegram): correct regex alternation precedence for 403 errors - Fix: /403.*(bot.*not.*member|bot was blocked)/ → /403.*(bot.*not.*member|bot.*blocked)/ - Ensures 403 requirement applies to both alternatives - Fixes Greptile review comment on PR openclaw#48650 * fix(telegram): add 'bot was kicked' to 403 error regex and message * fix(telegram): preserve membership delivery errors * fix: improve Telegram 403 membership delivery errors (openclaw#53635) (thanks @w-sss) --------- Co-authored-by: Ayaan Zaidi <hi@obviy.us>

@w-sss

… (thanks @w-sss) * fix(telegram): improve error messages for 403 bot not member errors - Detect 403 'bot is not a member' errors specifically - Provide actionable guidance for users to fix the issue - Fixes openclaw#48273 where outbound sendMessage fails with 403 Root cause: When a Telegram bot tries to send a message to a channel/group it's not a member of, the API returns 403 'bot is not a member of the channel chat'. The error message was not clear about how to fix this. Fix: 1. Detect 403 errors in wrapTelegramChatNotFoundError 2. Provide clear error message explaining the issue 3. Suggest adding the bot to the channel/group * fix(telegram): fix regex precedence for 403 error detection - Group alternatives correctly: /403.*(bot.*not.*member|bot was blocked)/i - Require 403 for both alternatives (previously bot.*blocked matched any error) - Update error message to cover both scenarios - Fixes Greptile review feedback * fix(telegram): correct regex alternation precedence for 403 errors - Fix: /403.*(bot.*not.*member|bot was blocked)/ → /403.*(bot.*not.*member|bot.*blocked)/ - Ensures 403 requirement applies to both alternatives - Fixes Greptile review comment on PR openclaw#48650 * fix(telegram): add 'bot was kicked' to 403 error regex and message * fix(telegram): preserve membership delivery errors * fix: improve Telegram 403 membership delivery errors (openclaw#53635) (thanks @w-sss) --------- Co-authored-by: Ayaan Zaidi <hi@obviy.us>

@w-sss

… (thanks @w-sss) * fix(telegram): improve error messages for 403 bot not member errors - Detect 403 'bot is not a member' errors specifically - Provide actionable guidance for users to fix the issue - Fixes openclaw#48273 where outbound sendMessage fails with 403 Root cause: When a Telegram bot tries to send a message to a channel/group it's not a member of, the API returns 403 'bot is not a member of the channel chat'. The error message was not clear about how to fix this. Fix: 1. Detect 403 errors in wrapTelegramChatNotFoundError 2. Provide clear error message explaining the issue 3. Suggest adding the bot to the channel/group * fix(telegram): fix regex precedence for 403 error detection - Group alternatives correctly: /403.*(bot.*not.*member|bot was blocked)/i - Require 403 for both alternatives (previously bot.*blocked matched any error) - Update error message to cover both scenarios - Fixes Greptile review feedback * fix(telegram): correct regex alternation precedence for 403 errors - Fix: /403.*(bot.*not.*member|bot was blocked)/ → /403.*(bot.*not.*member|bot.*blocked)/ - Ensures 403 requirement applies to both alternatives - Fixes Greptile review comment on PR openclaw#48650 * fix(telegram): add 'bot was kicked' to 403 error regex and message * fix(telegram): preserve membership delivery errors * fix: improve Telegram 403 membership delivery errors (openclaw#53635) (thanks @w-sss) --------- Co-authored-by: Ayaan Zaidi <hi@obviy.us>

@w-sss

… (thanks @w-sss) * fix(telegram): improve error messages for 403 bot not member errors - Detect 403 'bot is not a member' errors specifically - Provide actionable guidance for users to fix the issue - Fixes openclaw#48273 where outbound sendMessage fails with 403 Root cause: When a Telegram bot tries to send a message to a channel/group it's not a member of, the API returns 403 'bot is not a member of the channel chat'. The error message was not clear about how to fix this. Fix: 1. Detect 403 errors in wrapTelegramChatNotFoundError 2. Provide clear error message explaining the issue 3. Suggest adding the bot to the channel/group * fix(telegram): fix regex precedence for 403 error detection - Group alternatives correctly: /403.*(bot.*not.*member|bot was blocked)/i - Require 403 for both alternatives (previously bot.*blocked matched any error) - Update error message to cover both scenarios - Fixes Greptile review feedback * fix(telegram): correct regex alternation precedence for 403 errors - Fix: /403.*(bot.*not.*member|bot was blocked)/ → /403.*(bot.*not.*member|bot.*blocked)/ - Ensures 403 requirement applies to both alternatives - Fixes Greptile review comment on PR openclaw#48650 * fix(telegram): add 'bot was kicked' to 403 error regex and message * fix(telegram): preserve membership delivery errors * fix: improve Telegram 403 membership delivery errors (openclaw#53635) (thanks @w-sss) --------- Co-authored-by: Ayaan Zaidi <hi@obviy.us>

@w-sss

… (thanks @w-sss) * fix(telegram): improve error messages for 403 bot not member errors - Detect 403 'bot is not a member' errors specifically - Provide actionable guidance for users to fix the issue - Fixes openclaw#48273 where outbound sendMessage fails with 403 Root cause: When a Telegram bot tries to send a message to a channel/group it's not a member of, the API returns 403 'bot is not a member of the channel chat'. The error message was not clear about how to fix this. Fix: 1. Detect 403 errors in wrapTelegramChatNotFoundError 2. Provide clear error message explaining the issue 3. Suggest adding the bot to the channel/group * fix(telegram): fix regex precedence for 403 error detection - Group alternatives correctly: /403.*(bot.*not.*member|bot was blocked)/i - Require 403 for both alternatives (previously bot.*blocked matched any error) - Update error message to cover both scenarios - Fixes Greptile review feedback * fix(telegram): correct regex alternation precedence for 403 errors - Fix: /403.*(bot.*not.*member|bot was blocked)/ → /403.*(bot.*not.*member|bot.*blocked)/ - Ensures 403 requirement applies to both alternatives - Fixes Greptile review comment on PR openclaw#48650 * fix(telegram): add 'bot was kicked' to 403 error regex and message * fix(telegram): preserve membership delivery errors * fix: improve Telegram 403 membership delivery errors (openclaw#53635) (thanks @w-sss) --------- Co-authored-by: Ayaan Zaidi <hi@obviy.us>

openclaw-barnacle Bot added channel: telegram Channel integration: telegram size: XS labels Mar 24, 2026

greptile-apps Bot reviewed Mar 24, 2026

View reviewed changes

chatgpt-codex-connector Bot reviewed Mar 24, 2026

View reviewed changes

w-sss force-pushed the pr-48650 branch from 514e1d4 to 89d816e Compare March 24, 2026 14:07

chatgpt-codex-connector Bot reviewed Mar 24, 2026

View reviewed changes

obviyus force-pushed the pr-48650 branch from 89d816e to 3d7a491 Compare March 25, 2026 05:21

openclaw-barnacle Bot added agents Agent runtime and tooling size: S and removed size: XS labels Mar 25, 2026

obviyus self-assigned this Mar 25, 2026

w-sss and others added 6 commits March 25, 2026 10:56

fix(telegram): correct regex alternation precedence for 403 errors

6b0c95f

- Fix: /403.*(bot.*not.*member|bot was blocked)/ → /403.*(bot.*not.*member|bot.*blocked)/ - Ensures 403 requirement applies to both alternatives - Fixes Greptile review comment on PR openclaw#48650

fix(telegram): add 'bot was kicked' to 403 error regex and message

c944b63

fix(telegram): preserve membership delivery errors

a0f591c

fix: improve Telegram 403 membership delivery errors (openclaw#53635)…

f16e2b7

… (thanks @w-sss)

obviyus force-pushed the pr-48650 branch from 3d7a491 to f16e2b7 Compare March 25, 2026 05:28

obviyus merged commit 247f821 into openclaw:main Mar 25, 2026
11 checks passed

github-actions Bot mentioned this pull request Mar 25, 2026

📡 Upstream Digest — 2026-03-25 06:54 UTC curtismercier/openclaw-mods#357

Open

w-sss mentioned this pull request Mar 28, 2026

fix(telegram): improve 403 bot not member/blocked error messages #53631

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(telegram): improve error messages for 403 bot not member errors#53635

fix(telegram): improve error messages for 403 bot not member errors#53635
obviyus merged 6 commits intoopenclaw:mainfrom
w-sss:pr-48650

w-sss commented Mar 24, 2026

Uh oh!

greptile-apps Bot commented Mar 24, 2026

Uh oh!

greptile-apps Bot Mar 24, 2026

Uh oh!

greptile-apps Bot Mar 24, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

chatgpt-codex-connector Bot Mar 24, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

chatgpt-codex-connector Bot Mar 24, 2026

Uh oh!

Uh oh!

obviyus commented Mar 25, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

	if (/403.(bot.not.member\|bot.blocked)/i.test(errorMsg)) {
	if (/403.(bot.not.member\|bot.blocked\|bot.*kicked)/i.test(errorMsg)) {

		`Telegram send failed: bot is not a member of the chat or was blocked (chat_id=${params.chatId}).`,
		"Fix: Add the bot to the channel/group, or ensure it has not been removed/blocked by the user.",

Uh oh!

Conversation

w-sss commented Mar 24, 2026

Uh oh!

greptile-apps Bot commented Mar 24, 2026

Greptile Summary

Confidence Score: 4/5

Uh oh!

greptile-apps Bot Mar 24, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps Bot Mar 24, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot Mar 24, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot Mar 24, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

obviyus commented Mar 25, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants