Clone operation repeatedly pauses for ~30 minutes, while the same Telegram account cannot send messages

Describe the bug

Description

I'm cloning 70,000+ messages from one Telegram group to another using tdl forward --mode clone.

The clone runs normally for some time, but periodically it completely stops making progress for around 30 minutes before continuing.

During these pauses, I also cannot send messages from the normal Telegram mobile app using the same account. Once the tdl operation resumes, Telegram sending also appears to work again.

Question

Could these pauses be caused by Telegram FLOOD_WAIT / account-level API throttling?

If so, is there a recommended tdl setting or workflow for large --mode clone operations to reduce the frequency or duration of these pauses?

Is there a way for tdl to clearly report when it is waiting because of Telegram flood control, rather than appearing to be stuck?

Thanks.

To Reproduce

Command tdl forward --from source_chronological.json --to subtopic.txt --edit add_sender.txt --mode clone

Expected behavior

Observed behavior Large clone operation: 70,000+ messages Clone has been running for almost 24 hours Only around 50% has completed Periodically, tdl stops progressing for approximately 30 minutes During the same period, the normal Telegram client cannot send messages After the pause, tdl continues processing normally This happens repeatedly

Version

tdl version Version: 0.20.3 Commit: 9359aa2 Date: 2026-05-23T14:52:09Z

go1.25.8 windows/amd64

Which OS are you running tdl on?

Windows

Additional context

No response