Source: https://tgdog.wadesk.io/guide/troubleshooting/

[Home](https://tgdog.wadesk.io/)/ [Guide](https://tgdog.wadesk.io/guide/)/ Data & troubleshooting Data & troubleshooting

# Troubleshoot missing updates and Telegram API errors

Diagnose missing matches, receiver conflicts, rate limits and uncertain actions.

[TGDogProduct documentation](https://tgdog.wadesk.io/about/)Published Oct 9, 2026 Updated Oct 9, 2026 2 min read

AT A GLANCE
- Check reception and exemptions before changing rules.

- 409 means an update-receiver conflict; 429 requires waiting.

- Resolve uncertain actions before clearing local data.

## [When something doesn’t look right.](https://tgdog.wadesk.io/guide/troubleshooting/#when-something-doesnt-look-right)

### [No messages received](https://tgdog.wadesk.io/guide/troubleshooting/#no-messages-received)

Confirm Chrome is running and online, the token is valid, and the bot is an admin in the supergroup. Check whether another client or webhook is receiving updates. Telegram decides which messages a bot can see; do not assume it receives every kind of message.

### [A keyword seems to be missed](https://tgdog.wadesk.io/guide/troubleshooting/#a-keyword-seems-to-be-missed)

Check that the group and keyword rule are enabled, the sender is not exempt, and the message is present in the local cache. Use the extension’s missed-match diagnostics to inspect local reception and rule reasons. It does not fetch full history or trigger punishment.

### [409, 429, or an unknown action](https://tgdog.wadesk.io/guide/troubleshooting/#_409-429-or-an-unknown-action)

A 409 indicates an update-receiver conflict. Remove the conflict and manually resume. A 429 follows Telegram’s retry delay. An unknown action requires checking the execution record and, when needed, member state; do not treat it as completed.

[Source: Which messages can a bot receive?](https://core.telegram.org/bots/faq#what-messages-will-my-bot-get)

### [Still need a hand?](https://tgdog.wadesk.io/guide/troubleshooting/#still-need-a-hand)

[Contact us](https://tgdog.wadesk.io/contact/)

## [Check your setup](https://tgdog.wadesk.io/guide/troubleshooting/#check-your-setup)

- Check reception and exemptions before changing rules.

- 409 means an update-receiver conflict; 429 requires waiting.

- Resolve uncertain actions before clearing local data.

## [Where to go next](https://tgdog.wadesk.io/guide/troubleshooting/#where-to-go-next)

If you are setting up TGDog for the first time, follow the [complete How to use tutorial](https://tgdog.wadesk.io/how-to-use/). For a deeper explanation of another topic, return to the [Guide library](https://tgdog.wadesk.io/guide/).

TGDogTGDog product documentation. Written from the extension implementation and checked against official Telegram references.

[About the author](https://tgdog.wadesk.io/about/)

[← Previous articleMessage evidence, local storage and retention](https://tgdog.wadesk.io/guide/message-evidence/)