Line CLI shows a 401 or "not signed in" error during a session
On a 401 response, Line tries to refresh its sign-in once by itself. If that fails, it asks you to sign in: "Run /login to sign in."
Type /login, approve in the browser, then ask Line to continue. Your session and conversation are kept.
If it keeps happening, your account's sessions may have been signed out from the account's security settings, or your account may be paused under the abuse policy (see warnings and pauses in Line).
Related articles
Still need help?
Tried the steps above and still stuck? Email us. We usually reply within the first hour, and always within 24 hours. A full support team is with you.
Infrastructure questions, or permanent deletion of your data
infrastructure@clatterlabs.xyzFor deleting your whole account or the data of one service.