AFW-512 — Collector clock skew

Area: Cloud sync · All support codes · Reference table

Why this happened

The collector host's clock differs from the cloud's by more than two minutes. Skew breaks TLS certificate validation and token expiry in ways that look like auth failures.

Fix

Enable NTP on the collector host (timedatectl set-ntp true) and confirm with timedatectl status.

---

If the fix doesn't resolve it, file a support ticket from the console — your workspace's diagnostics snapshot is attached automatically, so this code reaches support with its context.