telegram api constructor · layer 229 · #a4bcc6fe
updates.channelDifferenceTooLong
The provided pts + limit < remote pts. Simply, there are too many updates to be fetched (more than limit), the client has to resolve the update gap in one of the following ways (assuming the existence of a persistent database to locally store messages):
definition
updates.channelDifferenceTooLong#a4bcc6fe flags:# final:flags.0?true timeout:flags.1?int dialog:Dialog messages:Vector<Message> chats:Vector<Chat> users:Vector<User> = updates.ChannelDifference;
parameters
| name | type | description |
|---|---|---|
flags | # | Flags, see TL conditional fields |
final | true | Whether there are more updates that must be fetched (always false) |
timeout | int | Clients are supposed to refetch the channel difference after timeout seconds have elapsed |
dialog | Dialog | Dialog containing the latest PTS that can be used to reset the channel state |
messages | Vector<Message> | The latest messages |
chats | Vector<Chat> | Chats from messages |
users | Vector<User> | Users from messages |
type
updates.ChannelDifference · other constructors: updates.channelDifferenceEmpty, updates.channelDifference
history
present in layers 46–229 · constructor id changed 3×
| id | layers |
|---|---|
| #5e167646 | 46 |
| #410dee07 | 62–70 |
| #6a9d7b35 | 71–98 |
| #a4bcc6fe | 99–229 |