Fix: a platform needs reconnecting

“Needs reconnect” means one of your platforms logged the session out, so ClientRadar can no longer read that feed. This is the most common — and easiest to fix — interruption. ClientRadar reads through your own logged-in browser sessions, so when a session ends, scanning for that platform pauses until you sign back in. It will not run silently in the background returning nothing; it tells you exactly which platform needs attention.

Why this happens

Platform sessions expire naturally over time. They can also end if you log out of that platform in another tab, on your phone, or on another computer — because that is the same account session ClientRadar was borrowing. None of this is a problem with your account; it just needs a fresh sign-in.

Fix it in four steps

1. Open the reconnect action. In ClientRadar, find the banner (or open the Networks health view) for the platform marked “Needs reconnect”, and click Reconnect for that platform — for example, “Reconnect X”.
2. Log back into the platform. The platform’s own login page opens in a new tab. Sign in there as you normally would, including any two-factor code. You are signing into your own account on the platform’s real login page — you never give ClientRadar a password.
3. Return to the ClientRadar tab. Switch back to the dashboard tab. That is the trigger — you do not need to click anything else.
4. Wait for the confirmation. ClientRadar re-checks the session, clears the banner, and shows a “reconnected” confirmation. Scanning for that platform resumes automatically.

If it comes straight back

If the banner returns immediately after you reconnect, you were likely logged out again — check that you are still signed in on the platform in that browser, and that you did not log out elsewhere. If a platform keeps dropping you every few minutes despite a good login, that points at something on the platform’s side rather than a simple logout; see Fix: a platform is updating.