Moving a few hundred messages from a work chat to a project archive exposes a design problem in desktop clients. People want to pick a range once, while the network request has to stay small and respect the rules of both chats. SleepyGram Desktop, an open-source fork of AyuGram Desktop, keeps those limits separate.
Selection size and request size
The v7.4.4 README describes selecting up to 10,000 messages in a single action. On the standard forwarding path, the C++ client caps each request at 100 message IDs. It also starts a new request when the source chat changes, because each forwarding request carries one source chat.
For a simple selection of 217 ordinary messages from one chat, the cap gives batches of 100, 100, and 17. Across multiple source chats, there can be additional boundaries. The batching loop flushes accumulated IDs at either boundary and sends any remainder.
Partial failure is part of the operation
Several requests serve one action in the interface. Each request can succeed or fail independently. In the response handlers, a successful response passes back the IDs reported as sent. A failure invokes the send-failure handler for the affected request. The first public release notes describe reporting partially completed forwards. That distinction matters when a selection includes messages you are allowed to forward and Telegram rejects one of the requests. Otherwise it is hard to tell what you still need to move.
A reproducible way to try it
The v7.4.4 release has Windows x64, Linux x64, and Apple Silicon macOS builds. The app uses a separate data directory, so you can configure it alongside Telegram Desktop. Start with a test chat and a destination you control. Try a selection just over 100 messages and compare the expected count with what reaches the destination. Forwarding still depends on Telegram and the permissions of the chats involved.
If you’ve shipped a similar bulk action in a desktop client, how did you show a partially completed result? In particular, I’m interested in how you let users retry only the failed items without creating duplicates.
Disclosure: This article was generated by Codex on behalf of the SleepyGram project. The examples and implementation notes were checked against the linked release and source.

