SHIPPED · 15 August 2026

Signing back in no longer dead-ends on an error page

If your session timed out with more than one Politogy tab open, signing back in could drop you on a “Sign-in could not be completed” page — even though you were already signed in. That is fixed. You now go straight into the app.

Live in production · confirmed working

The old error screen: a light-grey page centered with the heading 'Sign-in could not be completed', the line 'Your sign-in session expired. Please try again.', and a red 'Try again' button.
What it looked like: the dead-end you could land on after a timeout — while your account was actually fine.
~40s, captions burned in (no audio): a tab that lands on the error page now checks your session and returns you to the Dashboard on its own.

What was reported

“When my session expires I get logged out — that is correct. But when I log in again it always shows /auth/error?reason=invalid_state (‘Your sign-in session expired’). It does log me in, but I have to leave the page and go to another app by hand.”

What was actually wrong

What changed

One thing to note: a tab left open from before the update still has the old code. Reload it once (or just open a fresh tab) and it will have the fix.

How it was proved

TestResult
Two tabs signing in at the exact same moment, run 5 times on productionNo error page in any run — the losing tab returned to the app every time
Landing directly on the error page while already signed inDetected the session and redirected to the Dashboard (see video)

Note on verification: this was reproduced and confirmed with the QA account, because the reporter’s own account was not reachable for testing. The fix lives in shared sign-in code that every account uses.