fix(delivery-queue): enhance Telegram 'bot was kicked' error with helpful hints by kevinWangSheng · Pull Request #29085 · openclaw/openclaw

kevinWangSheng · 2026-02-27T19:33:59Z

Summary

When a cron job is configured to deliver to a Telegram Forum topic that restricts posting (e.g. topic:1 / General), the bot receives a 403: Forbidden: bot was kicked from the supergroup chat error. This message is identical to the error when the bot is actually removed from the group, making root cause analysis extremely difficult.

Fix

This PR adds a helper function enhanceErrorMessageWithHint() that:

Detects the 'bot was kicked' error pattern
Checks if the target includes a forum topic (:topic: syntax) or has a threadId set
If so, appends a helpful hint explaining that the error may indicate the topic restricts posting to admins only, not that the bot was removed from the group

Testing

Built successfully with `pnpm build"
The fix is applied in the delivery recovery path where permanent errors are handled

Closes #29048

- Add support for parsing code/code_block tags in rich text posts - Add support for parsing pre (preformatted text) tags with language - Handle share_chat message type for forwarded/merged messages Fixes: openclaw#28578

- Add resolveSystemdScope() to detect if service should run in user or system scope - Update resolveSystemdUnitPathForName() to use /etc/systemd/system for system scope - Add OPENCLAW_SYSTEMD_SCOPE env var to configure scope (default: user) fix(delivery-queue): enhance Telegram 'bot was kicked' error with helpful hints - Add enhanceErrorMessageWithHint() to provide context for forum topic errors - The 'bot was kicked' error is misleading when posting to locked forum topics - Now includes a hint explaining the topic may restrict posting to admins only Closes openclaw#29048 Closes openclaw#29051

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1c730dfec2

ℹ️ 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-02-27T19:36:50Z

+  const scope = resolveSystemdScope(env);
+  if (scope === "system") {
+    return path.posix.join("/etc/systemd/system", `${name}.service`);


Use matching systemctl scope for system units

When resolveSystemdUnitPathForName switches to /etc/systemd/system for OPENCLAW_SYSTEMD_SCOPE=system, the rest of src/daemon/systemd.ts still hard-codes systemctl --user (for example in assertSystemdAvailable and the install/manage flows), so system-scoped units are written to the system unit directory but controlled through the user manager. systemctl --help explicitly distinguishes --system (“Connect to system manager”) from --user (“Connect to user service manager”), so this path produces unit-not-found/reload failures whenever system scope is selected.

Useful? React with 👍 / 👎.

greptile-apps · 2026-02-27T19:36:59Z

Greptile Summary

This PR bundles three separate fixes into a single commit:

delivery-queue: Added enhanceErrorMessageWithHint() to provide context when Telegram returns "bot was kicked" errors for forum topics with restricted posting permissions
systemd: Added support for system-scope systemd services via OPENCLAW_SYSTEMD_SCOPE environment variable
feishu: Enhanced message parsing to handle code blocks (code, code_block, pre tags) and share_chat forwarded messages

The delivery-queue enhancement addresses issue #29048 by detecting when a delivery target includes a forum topic (:topic: syntax or threadId parameter) and appending a helpful hint explaining that the error may indicate posting restrictions rather than bot removal.

One logical issue found: the threadId validation incorrectly treats 0 as a valid thread ID, which could show the hint inappropriately.

Confidence Score: 4/5

This PR is mostly safe to merge with one minor logic bug
The changes are well-structured and address legitimate issues. The threadId validation bug is minor since threadId=0 is unlikely in practice, but should be fixed for correctness. All three fixes are independent and low-risk.
Pay close attention to src/infra/outbound/delivery-queue.ts:410-411 for the threadId validation logic

_{Last reviewed commit: 1c730df}

greptile-apps

_{3 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

greptile-apps · 2026-02-27T19:37:03Z

+  const hasTopic =
+    target.includes(":topic:") || (threadId !== undefined && threadId !== null && threadId !== "");


threadId=0 incorrectly treated as valid. 0 !== "" evaluates to true, causing the hint to appear even though 0 isn't a valid Telegram thread ID.

Suggested change

const hasTopic =

target.includes(":topic:") || (threadId !== undefined && threadId !== null && threadId !== "");

const hasTopic = target.includes(":topic:") || Boolean(threadId);

Prompt To Fix With AI

This is a comment left during a code review. Path: src/infra/outbound/delivery-queue.ts Line: 410-411 Comment: threadId=0 incorrectly treated as valid. `0 !== ""` evaluates to true, causing the hint to appear even though 0 isn't a valid Telegram thread ID. ```suggestion const hasTopic = target.includes(":topic:") || Boolean(threadId); ``` How can I resolve this? If you propose a fix, please make it concise.

When provider is 'local', doctor only checked local.modelPath for the model file path. But users can also configure the model via the generic 'model' field (e.g., hf:ggml-org/embeddinggemma-300m-qat-q8_0). This fix adds a hasModelAsLocalPath() function that checks if the model field contains hf: or http(s): paths, which are valid for local provider. Fixes openclaw#29099

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 416c88017a

ℹ️ 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-02-27T20:37:22Z

  // provider === "auto": check all providers in resolution order
-  if (hasLocalEmbeddings(resolved.local)) {
+  // Also check the model field for hf:/http(s): paths which work with local provider
+  if (hasLocalEmbeddings(resolved.local) || hasModelAsLocalPath(resolved.model)) {


Don’t treat memorySearch.model as local readiness in auto mode

The new hasModelAsLocalPath(resolved.model) short-circuit in auto mode can suppress the doctor warning even when no embedding provider is actually usable. If provider: "auto", local.modelPath is unset, and model is set to an hf:/http string, this branch returns early, but runtime auto-selection does not use memorySearch.model for local readiness (it only checks local.modelPath before trying local embeddings), so the gateway can still run without any embedding provider while openclaw doctor reports no issue.

Useful? React with 👍 / 👎.

openclaw-barnacle · 2026-03-05T04:03:57Z

This pull request has been automatically marked as stale due to inactivity.
Please add updates or it will be closed.

Kevin Shenghui added 2 commits February 27, 2026 11:29

fix(feishu): parse code blocks and share_chat messages

e294df9

- Add support for parsing code/code_block tags in rich text posts - Add support for parsing pre (preformatted text) tags with language - Handle share_chat message type for forwarded/merged messages Fixes: openclaw#28578

openclaw-barnacle Bot added gateway Gateway runtime channel: feishu Channel integration: feishu size: S labels Feb 27, 2026

chatgpt-codex-connector Bot reviewed Feb 27, 2026

View reviewed changes

greptile-apps Bot reviewed Feb 27, 2026

View reviewed changes

openclaw-barnacle Bot added the commands Command implementations label Feb 27, 2026

chatgpt-codex-connector Bot reviewed Feb 27, 2026

View reviewed changes

tyejcoleman mentioned this pull request Feb 27, 2026

tracking: Delivery reliability — silent message loss & recovery bugs #29143

Closed

openclaw-barnacle Bot added the stale Marked as stale due to inactivity label Mar 5, 2026

thewilloftheshadow closed this Mar 6, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

fix(delivery-queue): enhance Telegram 'bot was kicked' error with helpful hints#29085

fix(delivery-queue): enhance Telegram 'bot was kicked' error with helpful hints#29085
kevinWangSheng wants to merge 3 commits into
openclaw:mainfrom
kevinWangSheng:fix/systemd-system-service

kevinWangSheng commented Feb 27, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

chatgpt-codex-connector Bot Feb 27, 2026

Uh oh!

greptile-apps Bot commented Feb 27, 2026

Uh oh!

greptile-apps Bot left a comment

Uh oh!

greptile-apps Bot Feb 27, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

chatgpt-codex-connector Bot Feb 27, 2026

Uh oh!

openclaw-barnacle Bot commented Mar 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

		const hasTopic =
		target.includes(":topic:") \|\| (threadId !== undefined && threadId !== null && threadId !== "");

	const hasTopic =
	target.includes(":topic:") \|\| (threadId !== undefined && threadId !== null && threadId !== "");
	const hasTopic = target.includes(":topic:") \|\| Boolean(threadId);

Uh oh!

Conversation

kevinWangSheng commented Feb 27, 2026

Summary

Fix

Testing

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector Bot Feb 27, 2026

Choose a reason for hiding this comment

Uh oh!

greptile-apps Bot commented Feb 27, 2026

Greptile Summary

Confidence Score: 4/5

Uh oh!

greptile-apps Bot left a comment

Choose a reason for hiding this comment

Uh oh!

greptile-apps Bot Feb 27, 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 Feb 27, 2026

Choose a reason for hiding this comment

Uh oh!

openclaw-barnacle Bot commented Mar 5, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants