'Clear "pending_update_count" in Telegram Bot

I want to clear all pending_update_count in my bot!

The output of below command :

https://api.telegram.org/botxxxxxxxxxxxxxxxx/getWebhookInfo

Obviously I replaced the real API token with xxx

is this :

{
 "ok":true,"result":
    {
     "url":"",
     "has_custom_certificate":false,
     "pending_update_count":5154
    }
}

As you can see, I have 5154 unread updates til now!! ( I'm pretty sure this pending updates are errors! Because no one uses this Bot! It's just a test Bot)

By the way, this pending_update_count number are increasing so fast! Now that I'm writing this post the number increased 51 and reached to 5205 !

I just want to clear this pending updates. I'm pretty sure this Bot have been stuck in an infinite loop!

Is there any way to get rid of it?

P.S:

I also cleared the webhook url. But nothing changed!

UPDATE:

The output of getWebhookInfo is this :

{
   "ok":true,
   "result":{
      "url":"https://somewhere.com/telegram/webhook",
      "has_custom_certificate":false,
      "pending_update_count":23,
      "last_error_date":1482910173,
      "last_error_message":"Wrong response from the webhook: 500 Internal Server Error",
      "max_connections":40
   }
}

Why I get Wrong response from the webhook: 500 Internal Server Error ?

webhookstelegramtelegram-bottelegram-webhook


Solution 1:[1]

I think you have two options:

  1. set webhook that do nothing, just say 200 OK to telegram's servers. Telegram wiil send all updates to this url and the queque will be cleared.
  2. disable webhook and after it get updates by using getUpdates method, after it, turn on webhook again

Update:

Problem with webhook on your side. You can try to emulate telegram's POST query on your URL. It can be something like this:

{"message_id":1,"from":{"id":1,"first_name":"FirstName","last_name":"LastName","username":"username"},"chat":{"id":1,"first_name":"FirstName","last_name":"LastName","username":"username","type":"private"},"date":1460957457,"text":"test message"}

You can send this text as a POST query body with PostMan for example, and after it try to debug your backend.

Solution 2:[2]

For anyone looking at this in 2020 and beyond, the Telegram API now supports clearing the pending messages via a drop_pending_updates parameter in both setWebhook and deleteWebhook, as per the API documentation.

Solution 3:[3]

Just add return 1; at the end of your hook method.

Update:

Commonly this happens because of queries delay with the database.

Solution 4:[4]

I solved is like this

POST tg.api/bottoken/setWebhook to emtpy "url"
POST tg.api/bottoken/getUpdates
POST tg.api/bottoken/getUpdates with "offset" last update_id appeared before

doing this serveral times

POST tg.api/bottoken/getWebhookInfo

had a look if all away.

POST tg.api/bottoken/setWebhook with filled "url"

Solution 5:[5]

i solve it by Change file access permissions file - set permissions file to 755

and second increase memory limit in php.ini file

Solution 6:[6]

A quick&dirty way is to get a temporary webhook here: https://webhook.site/ and set your webhook to that (it will answer with a HTTP/200 code everytime, reseting your pending messages to zero)

Solution 7:[7]

I faced the same issue for my tele bot after user edited existing message. My bot receives update with editedMessage continuously, but update.hasMessage() was empty. As a result number of updates rocketly increased and my bot stack.

I solved this issue by adding handling for use case when message is missing - send 200 code:

    public APIGatewayProxyResponseEvent handleRequest(APIGatewayProxyRequestEvent event, Context context) {

        update = MAPPER.readValue(event.getBody(), Update.class);

        if (!update.hasMessage()) {
            return new APIGatewayProxyResponseEvent()
                    .withStatusCode(200) // -> !!!!!! return code 200
                    .withBody("message is missing")
                    .withIsBase64Encoded(false);
        }
        ... ... ...

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source
Solution 1
Solution 2 mcm69
Solution 3
Solution 4 theode
Solution 5 mamal
Solution 6 Juanan
Solution 7 OVelychko

Related Questions