Description

Running multiple Telegram bot accounts on a single OpenClaw instance generates massive getUpdates conflict errors — nearly 60,000 in one week.

Environment

• OpenClaw 2026.3.1
• 9 Telegram bot accounts (Fred, Penny, Atlas, Nova, Ace, etc.)
• Each bot bound to a different agent via bindings
• macOS, local mode

What happens

2026-02-28T02:46:55.429Z [telegram] getUpdates conflict; retrying in 4.1s.
2026-02-28T04:37:45.429Z [telegram] getUpdates conflict; retrying in 30s.
2026-02-28T07:39:24.429Z [telegram] getUpdates conflict; retrying in 30s.
...

$ grep -c 'getUpdates conflict' gateway.log
59986

Impact

• Log noise makes real issues hard to find
• Potential message delivery delays during conflict/retry cycles
• Unnecessary network overhead from retries

Expected behavior

• Each bot account should have its own isolated polling loop
• No conflicts between accounts since they use different bot tokens
• If conflicts are unavoidable, they should be logged at debug level, not info

Suggestion

• Ensure each Telegram account's polling is fully independent
• Reduce log level for getUpdates conflicts to debug/trace
• Consider webhooks as an alternative for multi-bot setups