Recovering after receiving types.UpdatesTooLong

[TrixiS]

Checklist

• I believe the idea is awesome and would benefit the framework
• I have searched in the issue tracker for similar requests, including closed ones

Description

It seems like pyrogram devs are dead or something. But here is the deal

2023-11-12 19:51:52,029 INFO Connecting...
2023-11-12 19:51:52,071 INFO Connected! Production DC2 (media) - IPv4
2023-11-12 19:51:52,072 INFO NetworkTask started
2023-11-12 19:51:52,223 INFO Session initialized: Layer 158
2023-11-12 19:51:52,223 INFO Device: CPython 3.10.11 - Pyrogram 2.0.106
2023-11-12 19:51:52,223 INFO System: Linux 5.15.0-69-generic (en)
2023-11-12 19:51:52,223 INFO Session started
2023-11-12 19:51:52,225 INFO PingTask started
2023-11-12 19:51:53,511 INFO PingTask stopped
2023-11-12 19:51:53,512 INFO Disconnected
2023-11-12 19:51:53,512 INFO NetworkTask stopped
2023-11-12 19:51:53,512 INFO Session stopped
2023-11-12 19:52:00,284 INFO {
    "_": "types.UpdatesTooLong"
}

Receiving this update leads to loosing some updates. So here is a question. How to handle such cases?