First-line fixes for missing zones, token scope gaps, partial visibility, build issues, and public-download or install problems.
- Token and capability diagnosis
- Zone and scan coverage issues
- Build and packaging issues
- Download and platform rollout expectations
Applies to
WindowsmacOSLinux
Covers
TroubleshootingConnectionsScansBuild
Troubleshooting
I validated the token but expected zones are missing
Check, in order:
- the token is tied to the intended account
- the token scope actually allows zone discovery
- the connection is saved in the workspace you think it is
The scan completed but coverage looks thin
That usually means one of these is true:
- the token lacks access to some Cloudflare surfaces
- analytics coverage is partial
- the selected scan profile was intentionally lighter
- the zone genuinely has little signal for that category
The product reports visibility gaps
That is correct behavior when the app cannot inspect a desired surface confidently.
A hosted installer downloads but the platform warning is confusing
Treat early-access platform warnings as part of the release workflow. What matters is that the artifact came from the official path and the docs explain the current warning flow.
When to escalate
Escalate when you can provide version, OS, install type, exact repro steps, expected vs actual result, redacted evidence, and the docs route already followed.