[Bug] get_chat_history raises 400 MESSAGE_IDS_EMPTY even when channel has message

[b1zya]

Checklist

• I am sure the error is coming from Pyrogram's code and not elsewhere
• I have searched in the issue tracker for similar bug reports, including closed ones
• I ran pip3 install https://github.com/TelegramPlayground/pyrogram/archive/dev.zip --force-reinstall and reproduced the issue using the latest development version

Description

Description of the issue

For the past 2-3 days, get_chat_history has been returning [400 MESSAGE_IDS_EMPTY] for specific channels. Previously, it worked fine, and I was able to retrieve messages correctly.

This issue does not occur for all channels, only for certain ones. The problem started suddenly, which suggests that there might have been a change in the Telegram API, breaking Pyrogram’s behavior.

I have tried rolling back to older versions of Pyrogram, all the way down to 2.2.2, but the issue persists.

Important Observation

I attempted to retrieve messages using raw Telegram API with messages.GetHistory, and it successfully returns messages.
However, when using get_chat_history(), I receive [400 MESSAGE_IDS_EMPTY].

I would like to emphasize that I am not a professional programmer and I use neural networks to write code.

But if there is any information I can provide for debugging and a more accurate answer, let me know. I will try to do my best.

Steps to reproduce

Here's a raw API method that works correctly outputs all messages from the channel. Messages succeeded in getting. This means that it has nothing to do with the channel's privacy settings:

async def get_history_raw(app, channel_id, channel_name):
"""Fetches messages using raw Telegram API and saves each response as a separate txt file."""
peer = await app.resolve_peer(channel_id)
history = await app.invoke(GetHistory(
peer=peer,
offset_id=0,
limit=50,
add_offset=0,
max_id=0,
min_id=0,
hash=0,
offset_date=0
))
print(history) # The response contains messages

Code example

Logs

[SpEcHiDe]

Can you share the chat where the error occurs?

[b1zya]

Can you share the chat where the error occurs?

Unfortunately, I cannot provide you with examples of channels or send you an invitation where this error occurs, as I am not an administrator there. These are non-public channels with access by invitation.
The thing is that I am a member of many such channels. Some of them have this problem and others are fine. I haven't found a pattern yet as to what it might be related to.

However, as I wrote above, trying to retrieve messages using the raw API works quite well.

Perhaps you could provide me with some sample code that I could debug and get a more detailed log than just the “400 MESSAGE_IDS_EMPTY” message

[SpEcHiDe]

from pyrogram import Client
app = Client("my_account")
app.start()
for m in app.get_chat_history(chat_id):
  print(m._raw)
app.stop()

Try run the above code by replacing the chat_id variable, then figure out which was the previous message where the error happened. Replace the id appropriately and share.

m = app.get_messages(chat_id=chat_id, message_ids=id)
print(m._raw)

[b1zya]

After long testing I am ready to say exactly, what exactly causes the problem and below I will describe the cause in detail. The problem occurs only when certain service messages are encountered in the chat history. If they appear in the path when trying to collect history, and also when trying to collect history by the id of that particular message, the error [400 MESSAGE_IDS_EMPTY] occurs.

Steps to Reproduce:

1. Call app.get_chat_history(chat_id, limit=10).
2. If a message appears in the chat history with type: “types.MessageService” - in my case it is a pinned message (types.MessageActionPinMessage) or another service message within the last limit messages, the entire request fails with a 400 MESSAGE_IDS_EMPTY error.
3. Even if I try app.get_messages(chat_id=chat_id, message_ids=message_id) on that specific service message ID, I still get the same 400 MESSAGE_IDS_EMPTY error.

Observed Behavior:

• If a normal text message is retrieved, everything works fine.
• If a pinned message (MessageActionPinMessage) appears in the chat history, get_chat_history() stops working completely and throws [400 MESSAGE_IDS_EMPTY].
• If I manually request that message ID using get_messages(), it also fails with the same error.
• However, calling the raw Telegram API method messages.GetHistory() returns the service message normally, meaning that Telegram does recognize the message but Pyrogram fails to handle it.

Additional Notes:

• This issue started appearing recently (~2-3 days ago).
• Step-by-step rollback and testing on all versions from Pyrogram 2.2.2 to Pyrogram 2.2.6 does not solve the problem.
• Using raw Telegram API (messages.GetHistory) does return the service message successfully.

Example of the problematic service message that causes failure:

{ "_": "types.MessageService", "id": 541, "peer_id": { "_": "types.PeerChannel", "channel_id": # Chanel Id }, "date": 1712912554, "action": { "_": "types.MessageActionPinMessage" }, "out": false, "mentioned": false, "media_unread": false, "reactions_are_possible": true, "silent": false, "post": true, "legacy": false, "reply_to": { "_": "types.MessageReplyHeader", "reply_to_scheduled": false, "forum_topic": false, "quote": false, "reply_to_msg_id": 444, "quote_entities": [] } }

[SpEcHiDe]

I tried in three chats and I did not encounter any issues even when the chat had pinned message service message in the history.

I guess you need to share details on how to reproduce this issue.

[b1zya]

I tried in three chats and I did not encounter any issues even when the chat had pinned message service message in the history.

I guess you need to share details on how to reproduce this issue.

There are some things going on that I can't figure out what it's related to.

I came and ran the script on another computer. It worked fine. I updated the python version. It started giving an error. But remarkably, after I reinstalled python and VsCode again from scratch, going back to the version on which everything worked, this error remained.

I realize I'm not giving any specifics. But I don't know where else to look.

[SpEcHiDe]

from pyrogram import Client
app = Client("my_account")
app.start()
for m in app.get_chat_history(chat_id):
print(m._raw)
app.stop()

Can you run this code and say at which message it raises the exception in your chat?

Then send a screenshot of the previous message using official TDesktop application

[b1zya]

from pyrogram import Client
app = Client("my_account")
app.start()
for m in app.get_chat_history(chat_id):
print(m._raw)
app.stop()

Can you run this code and say at which message it raises the exception in your chat?

Then send a screenshot of the previous message using official TDesktop application

I tried to execute this standard code. I get this traceback:

Traceback (most recent call last):
  File "/Users/user/Desktop/job/parsers/Suppliers_Parser/test_2", line 11, in <module>
    for m in app.get_chat_history(chat_id):
             ~~~~~~~~~~~~~~~~~~~~^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/pyrogram/sync.py", line 42, in async_to_sync_gen
    item, done = loop.run_until_complete(anext(agen))
                 ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/asyncio/base_events.py", line 725, in run_until_complete
    return future.result()
           ~~~~~~~~~~~~~^^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/pyrogram/sync.py", line 36, in anext
    return await agen.__anext__(), False
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/pyrogram/methods/messages/get_chat_history.py", line 149, in get_chat_history
    messages = await get_chunk(
               ^^^^^^^^^^^^^^^^
    ...<10 lines>...
    )
    ^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/pyrogram/methods/messages/get_chat_history.py", line 71, in get_chunk
    messages =await utils.parse_messages(
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<4 lines>...
    )
    ^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/pyrogram/utils.py", line 154, in parse_messages
    await types.Message._parse(
    ...<6 lines>...
    )
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/pyrogram/types/messages_and_media/message.py", line 1075, in _parse
    parsed_message.pinned_message = await client.get_messages(
                                    ^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<3 lines>...
    )
    ^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/pyrogram/methods/messages/get_messages.py", line 149, in get_messages
    r = await self.invoke(rpc, sleep_threshold=-1)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/pyrogram/methods/advanced/invoke.py", line 79, in invoke
    r = await self.session.invoke(
        ^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<4 lines>...
    )
    ^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/pyrogram/session/session.py", line 415, in invoke
    return await self.send(query, timeout=timeout)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/pyrogram/session/session.py", line 383, in send
    RPCError.raise_it(result, type(data))
    ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/pyrogram/errors/rpc_error.py", line 107, in raise_it
    raise getattr(
    ...<6 lines>...
      _raw=rpc_error)
pyrogram.errors.exceptions.bad_request_400.MessageIdsEmpty: Telegram says: [400 MESSAGE_IDS_EMPTY] (caused by "channels.GetMessages") Pyrogram 2.2.6 thinks: The requested message doesn't exist or you provided no message id

I tried replacing the "PyroTGFork" library with "kurigram".
Surprisingly, everything worked for me. I have no idea what exactly the reason could be. Is it some bug of the library or have I done something wrong in the system that now the code does not want to execute normally.

I tried running the code using “kurigram” and sending you an example of posts that cause an error using “PyroTGFork” and a post going by publication date right after it and not causing an error.But I've already thrown up an example of this message before:

In this example, the problem occurs with message ID 541:

{
    "_": "types.Message",
    "id": 553,
    "peer_id": {
        "_": "types.PeerChannel",
        "channel_id": # Chanel ID
    },
    "date": 1715618441,
    "message": "# Message in post",
    "out": false,
    "mentioned": false,
    "media_unread": false,
    "silent": false,
    "post": true,
    "from_scheduled": false,
    "legacy": false,
    "edit_hide": false,
    "pinned": false,
    "noforwards": false,
    "invert_media": false,
    "offline": false,
    "video_processing_pending": false,
    "entities": [],
    "views": 3985,
    "forwards": 3,
    "edit_date": 1738240203,
    "restriction_reason": []
}
{
    "_": "types.MessageService",
    "id": 541,
    "peer_id": {
        "_": "types.PeerChannel",
        "channel_id": # Chanel ID
    },
    "date": 1712912554,
    "action": {
        "_": "types.MessageActionPinMessage"
    },
    "out": false,
    "mentioned": false,
    "media_unread": false,
    "reactions_are_possible": true,
    "silent": false,
    "post": true,
    "legacy": false,
    "reply_to": {
        "_": "types.MessageReplyHeader",
        "reply_to_scheduled": false,
        "forum_topic": false,
        "quote": false,
        "reply_to_msg_id": 444,
        "quote_entities": []
    }
}

[b1zya]

from pyrogram import Client
app = Client("my_account")
app.start()
for m in app.get_chat_history(chat_id):
print(m._raw)
app.stop()

Can you run this code and say at which message it raises the exception in your chat?
Then send a screenshot of the previous message using official TDesktop application

I tried to execute this standard code. I get this traceback:

Traceback (most recent call last):
  File "/Users/user/Desktop/job/parsers/Suppliers_Parser/test_2", line 11, in <module>
    for m in app.get_chat_history(chat_id):
             ~~~~~~~~~~~~~~~~~~~~^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/pyrogram/sync.py", line 42, in async_to_sync_gen
    item, done = loop.run_until_complete(anext(agen))
                 ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/asyncio/base_events.py", line 725, in run_until_complete
    return future.result()
           ~~~~~~~~~~~~~^^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/pyrogram/sync.py", line 36, in anext
    return await agen.__anext__(), False
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/pyrogram/methods/messages/get_chat_history.py", line 149, in get_chat_history
    messages = await get_chunk(
               ^^^^^^^^^^^^^^^^
    ...<10 lines>...
    )
    ^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/pyrogram/methods/messages/get_chat_history.py", line 71, in get_chunk
    messages =await utils.parse_messages(
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<4 lines>...
    )
    ^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/pyrogram/utils.py", line 154, in parse_messages
    await types.Message._parse(
    ...<6 lines>...
    )
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/pyrogram/types/messages_and_media/message.py", line 1075, in _parse
    parsed_message.pinned_message = await client.get_messages(
                                    ^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<3 lines>...
    )
    ^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/pyrogram/methods/messages/get_messages.py", line 149, in get_messages
    r = await self.invoke(rpc, sleep_threshold=-1)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/pyrogram/methods/advanced/invoke.py", line 79, in invoke
    r = await self.session.invoke(
        ^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<4 lines>...
    )
    ^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/pyrogram/session/session.py", line 415, in invoke
    return await self.send(query, timeout=timeout)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/pyrogram/session/session.py", line 383, in send
    RPCError.raise_it(result, type(data))
    ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/pyrogram/errors/rpc_error.py", line 107, in raise_it
    raise getattr(
    ...<6 lines>...
      _raw=rpc_error)
pyrogram.errors.exceptions.bad_request_400.MessageIdsEmpty: Telegram says: [400 MESSAGE_IDS_EMPTY] (caused by "channels.GetMessages") Pyrogram 2.2.6 thinks: The requested message doesn't exist or you provided no message id

I tried replacing the "PyroTGFork" library with "kurigram". Surprisingly, everything worked for me. I have no idea what exactly the reason could be. Is it some bug of the library or have I done something wrong in the system that now the code does not want to execute normally.

I tried running the code using “kurigram” and sending you an example of posts that cause an error using “PyroTGFork” and a post going by publication date right after it and not causing an error.But I've already thrown up an example of this message before:

In this example, the problem occurs with message ID 541:

{
    "_": "types.Message",
    "id": 553,
    "peer_id": {
        "_": "types.PeerChannel",
        "channel_id": # Chanel ID
    },
    "date": 1715618441,
    "message": "# Message in post",
    "out": false,
    "mentioned": false,
    "media_unread": false,
    "silent": false,
    "post": true,
    "from_scheduled": false,
    "legacy": false,
    "edit_hide": false,
    "pinned": false,
    "noforwards": false,
    "invert_media": false,
    "offline": false,
    "video_processing_pending": false,
    "entities": [],
    "views": 3985,
    "forwards": 3,
    "edit_date": 1738240203,
    "restriction_reason": []
}
{
    "_": "types.MessageService",
    "id": 541,
    "peer_id": {
        "_": "types.PeerChannel",
        "channel_id": # Chanel ID
    },
    "date": 1712912554,
    "action": {
        "_": "types.MessageActionPinMessage"
    },
    "out": false,
    "mentioned": false,
    "media_unread": false,
    "reactions_are_possible": true,
    "silent": false,
    "post": true,
    "legacy": false,
    "reply_to": {
        "_": "types.MessageReplyHeader",
        "reply_to_scheduled": false,
        "forum_topic": false,
        "quote": false,
        "reply_to_msg_id": 444,
        "quote_entities": []
    }
}

To be honest, I myself cannot understand what exactly causes this error.

As I wrote above, on another computer with a slightly earlier version of python installed, I was able to run the code successfully. After updating Python, the error started to appear. However, when I tried to go back to the version of Python where everything was running successfully, the error remained. Which surprised me a lot. In the end, the code stopped working on the second computer as well

[SpEcHiDe]

can you try

await app.get_messages(chat_id=, reply_to_message_ids= 541)

and

await app.get_messages(chat_id=, message_ids=444)

[SpEcHiDe]

also, can you try if this works for you pip install --force-reinstall https://github.com/TelegramPlayGround/pyrogram/archive/706609340337df179bfac25fbb0a3705608b95bd.zip

[b1zya]

can you try

await app.get_messages(chat_id=, reply_to_message_ids= 541)

and

await app.get_messages(chat_id=, message_ids=444)

Tests on PyroTGFork 2.2.6:
I have tested app.get_messages(chat_id=chat_id, message_ids=444) and app.get_messages(chat_id=chat_id, reply_to_message_ids=541) and I get a reply as message_ids=444 in both cases. Since in the case of reply_to_message_ids=541 we are actually referring to message_ids=444. The response is successful. There is no point in saving the log.

I still get an error when trying to execute app.get_messages(chat_id=chat_id, message_ids=541):
“Telegram says: [400 MESSAGE_IDS_EMPTY] (caused by “channels.GetMessages”) Pyrogram 2.2.6 thinks: The requested message doesn't exist or you provided no message id”

[SpEcHiDe]

I still get an error when trying to execute app.get_messages(chat_id=chat_id, message_ids=541):

and, you do not get this error when you use kurigram ?

[b1zya]

I still get an error when trying to execute app.get_messages(chat_id=chat_id, message_ids=541):

and, you do not get this error when you use kurigram ?

also, can you try if this works for you pip install --force-reinstall https://github.com/TelegramPlayGround/pyrogram/archive/706609340337df179bfac25fbb0a3705608b95bd.zip

Tests on the PyroTGFork build you suggested:

Tested
app.get_chat_history(chat_id, limit = 10)
and
app.get_messages(chat_id=chat_id, message_ids=541)

It works adequately. I get a successful response. In the same format as with the “kurigram” library from the answer above.

The proposed PyroTGFork build worked and helped.

[SpEcHiDe]

Can you retest once more using this command pip install --force-reinstall --no-cache-dir https://github.com/TelegramPlayGround/pyrogram/archive/gmrrr.zip ?