openclaw - 💡(How to fix) Fix Feature Request: Add startupConcurrency and startupDelayMs for multi-account Telegram channel initialization [1 comments, 2 participants]

Is your feature request related to a problem? Please describe.

When configuring multiple Telegram bot accounts (I have 16), the Gateway experiences severe event loop starvation during startup. All accounts call getMe simultaneously in a Promise.all fashion, which completely saturates the Node.js single-threaded event loop.

Evidence from production logs (16 Telegram bots):

subsystem: fetch-timeout
operation: fetchWithTimeout
url: https://api.telegram.org/bot.../getMe
timeoutMs: 10000
elapsedMs: 149709
timerDelayMs: 139709
eventLoopDelayHint: "timer delayed 139709ms, likely event-loop starvation"

Describe the solution you'd like

A configuration option to limit concurrency or stagger the startup of multiple Telegram bot accounts. Something like:

{
  "channels": {
    "telegram": {
      "startupConcurrency": 4,
      "startupDelayMs": 1000
    }
  }
}

• startupConcurrency: Maximum number of accounts to initialize simultaneously (default: unlimited / current behavior)
• startupDelayMs: Delay between each batch of accounts (default: 0)

This would prevent all getMe probes from hitting the event loop at once, allowing timers to fire on schedule and avoiding cascading fetch timeouts.

Describe alternatives you've considered

Additional context

• OpenClaw Version: 2026.5.4 (325df3e)
• Platform: Windows 11 x64, Node.js 25.9.0
• Number of Telegram accounts: 16 (each bound to a different agent)
• Impact: Startup takes 2-3 minutes with dozens of false-positive timeout warnings. Once the event loop recovers, runtime is normal.
• Relevant log phase: channels.telegram.start-account

This is a quality-of-life improvement for users running multi-agent setups with many Telegram bots. The fix would be a simple p-limit or sequential for loop wrapping the account initialization logic in the channel bootstrap.