search

LonamiWebs / Telethon

Pure Python 3 MTProto API Telegram client library, for bots too!
https://docs.telethon.dev
MIT License
10.09k stars 1.41k forks source link

Telegram Persistent Timestamp Outdated Error and GetChannel Difference Request errors #4442

Open ZWECE opened 3 months ago

ZWECE commented 3 months ago

Description

Hello,

I have many bot versions. My bot runs each account in a loop with joining the group, sending messages and adding reactions to messages.

2 days ago my v1/v7 versions all give the following issue. My bots that have been running for 3 months without interruption are giving this problem even though I have not made any changes.

What did I do?

Proxy, device, Mac address, phone numbers, wiretapped or unwiretapped session files, different apis, ignoring issues, windows time settings, creating new session files and hundreds of other changes and tests.

1 API key had the power to process my 8 accounts every 10 seconds.

What changed in Telegram and how can I solve the problem?

Thanks for your help.

Telegram is having internal issues PersistentTimestampOutdatedError: Persistent timestamp outdated (caused by GetChannelDifferenceRequest)

Getting difference for channel updates 1645141274 caused ValueError; ending getting difference prematurely until server issues are resolved

Checklist

Lonami commented 3 months ago

What changed in Telegram and how can I solve the problem?

Don't know, but you're not the first to report a similar problem. It might've been some temporary issues. It might be deeper changes in how Telegram works.

I unfortunately doubt I'll investigate this any time soon though.

ZWECE commented 3 months ago

It's very important that I find out what caused this mistake. I can't say whether it was the telegram or not. It happened after he was arrested. It seems like a waste of time to wait.

ShnurD6 commented 3 months ago

Same situation, errors like this for the last 3 days

[WARNING/2024-08-29 15:17:05,587] Getting difference for channel updates 123456 caused PersistentTimestampInvalidError; ending getting difference prematurely until server issues are resolved
[WARNING/2024-08-29 15:19:37,309] Server closed the connection: 0 bytes read on a total of 8 expected bytes
[WARNING/2024-08-29 15:28:56,659] Getting difference for channel updates 123456 caused PersistentTimestampInvalidError; ending getting difference prematurely until server issues are resolved

My bots had been running for about a year, but I had never gotten these errors in such numbers before.

ZWECE commented 3 months ago

@ShnurD6

I've realized more than 200 scenarios and the result is close to impossible. I'm making one last attempt.

I'm changing the coding to run with GPT4 and Pyrogram library, not Telethon, if there is a problem there, which there won't be. We have a problem in Telegram.

bupabupala commented 3 months ago

I encountered the same issue but couldn't figure out where the problem is. I have a service that randomly requests get_dialogs every 1-5 minutes as a heartbeat, but it resulted in such a warning.

annatelegina commented 3 months ago

The same problem

rsking01 commented 1 week ago

Same problem

Tran97 commented 5 hours ago

@ShnurD6

I've realized more than 200 scenarios and the result is close to impossible. I'm making one last attempt.

I'm changing the coding to run with GPT4 and Pyrogram library, not Telethon, if there is a problem there, which there won't be. We have a problem in Telegram.

Update on this?