Troubleshooting
Real failure signatures from Account Platform, what they mean, and how to check.
"Connected" in the database, but nothing is syncing
Symptom: an account shows as connected, sync progress never moves.
Cause: the database row can say connected while the process actually
collecting data for that account is dead. An old or blank last_ok
timestamp is not proof of a stall on its own — it resets to blank on every
normal collector respawn, so a fresh restart looks identical to a real
freeze if you only look at that field.
Check: the account's isAuth marker, not last_ok. isAuth != true is
the actual signal a collector has stopped. See
Check sync status for the full
picture of what the sync chip shows.
A proxy address rotation "succeeded" but the tab is still on the old one
Symptom: you rotated an account's egress address, TEASE reports success, but the browser session still behaves like it's on the previous IP.
Cause: rotating an address is two calls in a fixed order (ask the
provider, then bump an internal generation counter) because the real exit IP
changes without host:port changing, and every session lock compares
host:port. If the second call fails after the first succeeds, the address
has moved but nothing has told the tab yet.
Check: TEASE reports this drifted state explicitly rather than showing a bare success — if you see that warning, treat the account as needing a fresh check. See Rotate an account's egress proxy.
A second device can't take over a live session
Symptom: opening the same account from a different installation fails or conflicts instead of quietly taking over.
Cause: an activity lease is bound to a specific installation and expires on a short TTL (30 seconds) if not renewed. A live local context still holding the row on another device is a real, reported conflict — not a bug — because handing a live session to a second device without coordination is exactly the failure this exists to prevent.
Check: wait for the lease to expire naturally, or close the session on the original device before opening it elsewhere.
What's next
Something not covered here that looks like a bug? Check Boundaries first — it may be a Club, Link, or Stream concern routed through an account you connected here.