Fix: a platform is in a protective cooldown
A protective cooldown means ClientRadar paused a platform to keep your account safe. It resumes automatically at the time shown — and you can override it if you're sure it's a false alarm.
A protective cooldown means ClientRadar paused scanning on a platform on purpose, to keep your account safe after a warning sign — for example a soft-block or a rate signal from the platform. This is the safety layer doing its job. It is not a ban, and you do not have to do anything: scanning resumes automatically at the time shown.
Why ClientRadar pauses
The platforms watch for accounts that act too fast or too much like automation. When ClientRadar sees an early warning — a soft-block, an unusual response, a rate limit — it steps back for a while rather than pushing on and risking a real restriction. Pausing briefly now is how you avoid a much longer problem later. That is the whole point of the safety layer: keep you under the radar.
Because this is intentional, it is shown as its own state with a clear resume time, separate from “needs reconnect” (a logout you fix by signing in) and “platform updating” (a change on the platform’s side).
When it resumes
The cooldown shows both an absolute and a relative resume time — for example, “Resumes Fri 14:00 (in ~3h)”. When that time arrives, scanning for the platform starts again on its own. You do not need to keep the dashboard open or check back; it clears itself.
Your other platforms are unaffected. A cooldown on one network does not pause the others — a “Scan now” will still cover the healthy platforms and tell you which one was skipped and why.
If you’re sure it’s a false alarm
ClientRadar keeps you in control, so there is a way to resume early — but it is deliberately not a one-tap button. A “resume early” option sits behind an explicit warning that overriding a protective pause raises the risk to your account, and your choice is recorded. Only use it if you are confident the pause was a false positive. If you are not sure, the safest thing is to let the cooldown run to its resume time.
Still stuck?
If a platform keeps entering cooldown, or the resume time never seems to arrive, open Help & support in the ClientRadar sidebar and export a diagnostic bundle so we can see what triggered it.