Background tasks

WM Guard counts significantly overdue WP-Cron events. When Action Scheduler is available—for example through WooCommerce—its overdue queue can also be considered.

REST and loopback

After optional online diagnostics are allowed, WM Guard uses self-HTTP requests to check whether the REST API and a loopback request basically work. Results are cached.

Outbound connectivity

For general outbound connectivity, WM Guard does not send a separate probe to an external service. Instead, it checks whether WordPress has successfully refreshed its normal update information within the last two days.

Without online permission, REST and loopback results remain deliberately unknown rather than being shown as successful.