#telegram sendMessage failed

1 messages · Page 1 of 1 (latest)

leaden verge
#

I'm facing

20:59:13 [telegram] sendMessage failed: Network request for 'sendMessage' failed!
20:59:13 [telegram] telegram final reply failed: HttpError: Network request for 'sendMessage' failed!
20:59:14 [telegram] sendMessage failed: Network request for 'sendMessage' failed!
20:59:14 [telegram] telegram message processing failed: HttpError: Network request for 'sendMessage' failed!
20:59:32 [telegram] [diag] polling cycle error reason=getUpdates conflict inFlight=0 outcome=ok startedAt=1776430770202 finishedAt=1776430772221 durationMs=2019 offset=0 err=Call to 'getUpdates' failed! (409: Conflict: terminated by other getUpdates request; make sure that only one bot instance is running)
20:59:32 [telegram] getUpdates conflict: Call to 'getUpdates' failed! (409: Conflict: terminated by other getUpdates request; make sure that only one bot instance is running); retrying in 30s.

I have 4 agents and each of it has telegram bot binded.

jolly spruceBOT
upbeat hedgeBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

vernal hamletBOT
#

First, please paste openclaw --version.

The 409 getUpdates conflict is the big clue here. It means the same Telegram bot token is being consumed by more than one active updater.

With OpenClaw, Telegram is owned by the gateway process, not by each agent separately. So 4 agents is fine, but only in these patterns:

  1. 4 different Telegram bot tokens, one per channels.telegram.accounts.<id>.botToken, then route with bindings
  2. 1 Telegram bot token total, then route chats/topics to different agents with bindings or channels.telegram.groups.<chatId>.topics.<threadId>.agentId

What breaks is:

  • same bot token configured in multiple accounts/agents
  • two OpenClaw gateways/containers running at once
  • another app/webhook/poller using the same Telegram bot token

So I’d check these next:

# 
openclaw status
openclaw gateway status
openclaw channels status --probe
openclaw logs --follow

Also verify:

  • only one OpenClaw runtime is running
  • each channels.telegram.accounts.*.botToken is unique
  • if you intended multi-account Telegram, your bindings match those account ids

The sendMessage failed: Network request... part is usually a separate network issue to api.telegram.org (DNS, IPv6, proxy, VPS egress). Fix the 409 first. If send failures remain after that, then look at Telegram network config.

Please paste these, redacting tokens: