A code request on every connection means one thing: the session is not being saved, so a new one is created each time. To Telegram that looks like a new device.
Why it matters
An account logging in «from a new device» daily behaves like a stolen one. Telegram responds predictably: heightened scrutiny first, restrictions after. One extra authorisation means nothing; ten in a row is a signal.
Three causes
- The session file is not persisted. Write permissions, a full disk, a temporary folder — the session is created and disappears.
- The same session runs in two places. Each instance invalidates the other.
- The proxy changes every time. A login from a new country prompts a code even on a live session.
How to check
Connect, wait for success, disconnect and connect again. A second code request points at file persistence. No second request points at the proxy or a parallel instance.
What to do
Pin one proxy to the account and stop changing it. Make sure the account is not running in two places — one account lives in one place. Then give it a quiet week: heightened attention from Telegram is cleared by time, not by activity.
The limits worth keeping low during that week are in the warm-up calculator.