The Wordfence scan scheduler tries to contact Wordfence servers using wp_remote_post. The request stops before it finishes. This happens when the server aborts the connection or the PHP process exceeds its time limit. The result is a failed cron event and no new scan data.
Typical triggers include low PHP max_execution_time, server‑level timeout settings, blocked outbound traffic, DNS lookup failures, or SSL handshake problems. Each of these prevents the remote POST from completing.