8 replies

After adding new telegram bot / new api key, openclaw doesn't receive messages

✅Solved

outbound test with

openclaw message send --channel telegram --target <my_telegram_id> --message "telegram outbound test"

openclaw message send --channel telegram --target <my_telegram_id> --message "telegram outbound test"

worked fine, and

TOK="$(openclaw config get channels.telegram.botToken)"
watch -n 1 "curl -s https://api.telegram.org/bot${TOK}/getUpdates?limit=1"

TOK="$(openclaw config get channels.telegram.botToken)"
watch -n 1 "curl -s https://api.telegram.org/bot${TOK}/getUpdates?limit=1"

Also works to receive messages.

But nothing appears in the logs of

openclaw logs --follow --plain --max-bytes 1000000

openclaw logs --follow --plain --max-bytes 1000000

and similar commands, it doesn't appear like openclaw gets anything.

Solution

That exact combo (“probe healthy”, webhook empty, but

lastInboundAt: null

lastInboundAt: null

right after swapping to a new bot token) strongly suggests an offset mismatch:

OpenClaw persists the last seen Telegram

update_id

update_id

in the state dir:

-

~/.openclaw/telegram/update-offset-<accountId>.json

~/.openclaw/telegram/update-offset-<accountId>.json

(

accountId

accountId

is usually

default

default

)

If you previously ran a different bot on the same accountId, the stored

lastUpdateId

lastUpdateId

can be way higher than the new bot’s update stream (new bots start low) → OpenClaw polls with an offset “in the future” and will never receive anything.

Fix (safe + reversible)

On the gateway host:

ls -la ~/.openclaw/telegram
cat ~/.openclaw/telegram/update-offset-default.json 2>/dev/null || true

ls -la ~/.openclaw/telegram
cat ~/.openclaw/telegram/update-offset-default.json 2>/dev/null || true

Jump to solution

FotC�

Friends of the Crustacean 🦞🤝•3w ago•

8 replies

dante

After adding new telegram bot / new api key, openclaw doesn't receive messages

✅Solved

outbound test with

openclaw message send --channel telegram --target <my_telegram_id> --message "telegram outbound test"

openclaw message send --channel telegram --target <my_telegram_id> --message "telegram outbound test"

worked fine, and

TOK="$(openclaw config get channels.telegram.botToken)"
watch -n 1 "curl -s https://api.telegram.org/bot${TOK}/getUpdates?limit=1"

TOK="$(openclaw config get channels.telegram.botToken)"
watch -n 1 "curl -s https://api.telegram.org/bot${TOK}/getUpdates?limit=1"

Also works to receive messages.

But nothing appears in the logs of

openclaw logs --follow --plain --max-bytes 1000000

openclaw logs --follow --plain --max-bytes 1000000

and similar commands, it doesn't appear like openclaw gets anything.

Solution

That exact combo (“probe healthy”, webhook empty, but

lastInboundAt: null

lastInboundAt: null

right after swapping to a new bot token) strongly suggests an offset mismatch:

OpenClaw persists the last seen Telegram

update_id

update_id

in the state dir:

-

~/.openclaw/telegram/update-offset-<accountId>.json

~/.openclaw/telegram/update-offset-<accountId>.json

(

accountId

accountId

is usually

default

default

)

If you previously ran a different bot on the same accountId, the stored

lastUpdateId

lastUpdateId

can be way higher than the new bot’s update stream (new bots start low) → OpenClaw polls with an offset “in the future” and will never receive anything.

Fix (safe + reversible)

On the gateway host:

ls -la ~/.openclaw/telegram
cat ~/.openclaw/telegram/update-offset-default.json 2>/dev/null || true

ls -la ~/.openclaw/telegram
cat ~/.openclaw/telegram/update-offset-default.json 2>/dev/null || true

Jump to solution

After adding new telegram bot / new api key, openclaw doesn't receive messages

Fix (safe + reversible)

Similar Threads

After adding new telegram bot / new api key, openclaw doesn't receive messages

Fix (safe + reversible)

Similar Threads

Similar Threads

Similar Threads