Well, that’s a big lie.
Updating from 4.2.3 to 4.2.4 breaks the “Prevent caching of objects after settings change” feature: so now every resource is followed by a query. Not to mention the others well known bugs like CloudFlare API not working and so on. How can they even state it’s compatible? Ridiculous.
Another thing I’ve recently discovered is that the “Cache Preload” feature doesn’t use any user-agent (they usually put “W3 Total Cache/0.9.X.X”) for fetching the pages on the web-site, thus it generates 500 errors in the access_log if you have rules for blocking that kind of requests, which happened to me having iTSec plugin installed for security.
Honestly I’m quite disappointed seeing how poorly supported is this plugin, which is just the most popular one for caching on WordPress.