Search⌘K

Why do I keep getting logged out or stuck in a login loop?

Plain-language version of common 401 / login-loop causes and what to try.

Most of the time it's one of two harmless things: your sign-in expired (sessions last 5 days), or your browser is blocking the cookie that keeps you signed in. Try logging out and back in first — if that bounces you straight back to the login screen, the cookie is the culprit.

What's happening

When you sign in, ZiplineOS gives your browser a token — a cookie called __session. Every request carries that cookie to prove who you are. If it's missing, expired, or blocked, the system treats you as a stranger and redirects you to login. The loop happens because the cookie isn't sticking, not because your password is wrong.

The three usual causes

What you're seeingWhat it meansWhat to try
Signed in earlier, now logged outSession expired (5 days)Sign in again
Log in, immediately bounced back — over and overBrowser blocking the sign-in cookieSee steps below
Whole team logged out at onceRecent update or short outageWait a few minutes, sign in again

Session expiry is normal and expected — signing back in fixes it completely.

Cookie blocked — the sign-in cookie must be shared across ZiplineOS portals. Strict privacy settings, ad/privacy extensions, or Safari's tracking protection can block this, causing the loop.

Update or outage — after a deployment, existing sessions can be invalidated all at once. It self-corrects on the next sign-in.

If you're stuck in a loop

Work through these in order:

  1. Sign out fully, then sign back in. Clears a stale or expired session.
  2. Try a normal browser window with default privacy settings — not incognito, extensions paused. If it works here, a privacy setting was blocking the cookie.
  3. Allow cookies for ZiplineOS in your browser's privacy settings. Safari users may need to turn off "Prevent cross-site tracking" for ZiplineOS.
  4. Try Chrome with default settings. If the loop disappears, the issue is your other browser's configuration.

If a fresh Chrome window fixes it, the problem is a privacy/cookie setting in your usual browser — not your account. No need to wait on support.

When to contact support

  • You've tried the steps above and are still looping.
  • Multiple people on your team are locked out and it hasn't cleared within a few minutes.
  • Your account shows as deactivated — that's intentional and needs an admin to reactivate.

When you contact support, mention: when it started, whether it's just you or the whole team, and which browser you're using.