Fix: a platform is updating
"Platform updating" means a network changed something on their side and ClientRadar is shipping a fix. Usually there's nothing to do — scanning resumes automatically. Here's why.
“Platform updating” means the network — Facebook, Reddit, X or LinkedIn — changed something on their side that affects how ClientRadar reads their feed, and a fix is on the way. This is a maintenance state, not a warning about your account. In most cases there is nothing for you to do.
What’s actually happening
Platforms change their internal machinery from time to time — the identifiers and request shapes ClientRadar relies on to read a feed the same way your browser does. When one of those changes, scanning for that platform can temporarily stop working correctly. Rather than run silently and return nothing, ClientRadar names the state honestly: the platform changed, and an update is coming.
This is deliberately shown as its own state, separate from “needs reconnect” (which you fix by logging in) and “protective cooldown” (which is the safety layer pausing on purpose). “Platform updating” is neither — it is on ClientRadar to fix, not you.
What to do
In almost every case: nothing. The fix for a platform change usually ships as a server-side update that reaches your extension automatically — no reinstall, no settings to change. Scanning for that platform resumes on its own once the update lands. You do not need to keep re-checking; the state clears itself when it is fixed.
The one thing worth doing is a quick sanity check that you are still logged into that platform in your browser, so scanning can resume the moment the fix arrives. If the platform shows “needs reconnect” instead, follow Fix: a platform needs reconnecting.
If it stays this way for a long time
These changes are treated as a priority, so a platform should not sit in “updating” indefinitely. If it does, and especially if every platform is affected at once, something local may be interfering with ClientRadar’s requests. That is a good moment to send us a diagnostic bundle — open Help & support in the ClientRadar sidebar and export it, so we can see exactly what your extension is encountering.