Hi @bayejid00,
Errors such as this are often picked up in Query Monitor for our intended silent failures. We sometimes utilize WordPress’ $wpdb->suppress_errors(true); function or PHP’s @ in situations we know an error may occur. These tools tend to ignore those whereas they’d normally not show to any customers or their site’s visitors, and are non-fatal warnings to the operation of your site.
There’s no fixed amount of resources we know Wordfence will use on each customer’s server. Therefore, some non-critical situations where it’s more expensive on resources to retry or check for the presence of a file/record first, we simply choose to fail silently and continue.
Thanks,
Peter.
