#Second Telegram account shows “Last inbound: n/a” and doesn’t respond

1 messages · Page 1 of 1 (latest)

late driftBOT
#

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

rapid slateBOT
#

Your config pattern for multi‑Telegram + bindings by accountId looks right (it matches the docs example), so “Last inbound: n/a” on just the 2nd bot almost always means that bot isn’t actually receiving updates from Telegram (not a routing/binding problem).

Here’s the fastest way to pinpoint why:

0) Version (matters for multi-account edge cases)

Paste:

openclaw --version

1) Probe both Telegram accounts (verifies token + shows webhook state)

Run inside the container/VPS:

openclaw channels status --probe --json

You’re looking (for BOTH default and trader) for:

#
  • probe.ok: true
  • probe.bot.username matches the bot you think it is
  • probe.webhook.url

If probe.ok is false for trader → token/config/env resolution issue (wrong token, wrong config file mounted, etc.).

If probe.webhook.url is non-empty for trader → that bot is in webhook mode right now, and long-polling won’t receive updates. Either:

  • clear the webhook for that bot token, or
  • switch OpenClaw to webhook mode properly (requires public ingress + channels.telegram.webhookSecret etc.)

(Ref: Telegram docs + webhook section: https://docs.openclaw.ai/channels/telegram)

2) Tail logs while messaging the 2nd bot

In one terminal:

openclaw logs --follow
#

Then DM the trader bot /start (or any message).

Common signatures:

  • 409 getUpdates conflict → something else is polling the same bot token (another container, old process), or webhook is still set.
  • “can’t use getUpdates while webhook is active” → webhook set (same fix as above).
  • 401/Unauthorized → bad token.

3) If you manually edited the token in the config: reset the polling offset (very common)

If the trader bot token was ever swapped manually (edit file / redeploy), OpenClaw might have a stale per-account offset file and you can end up with “no inbound ever”.

Fix options:

  • Re-add the account via CLI (this clears the offset on token change):
    openclaw channels add --channel telegram --account trader --token <BOT_TOKEN>
  • Or delete the offset file for that account (then restart gateway). Default state dir is ~/.openclaw (or whatever OPENCLAW_STATE_DIR is):
    • .../telegram/update-offset-trader.json
#

If you paste one thing…

Paste the Telegram section of:

openclaw channels status --probe --json

(redact tokens), and I can tell you immediately whether this is webhook/conflict/token/offset.

shell bloom
#

@rapid slate