Reply

So far, the only reason for this to happen was the limitation on the hosting site that causes process to timeout. Some operations, in some cases might use more resources, so plugin attempts to increase PHP limit and timeout to make sure it works. But, some (less reputable, in my experience) hosting companies impose the hard limit to PHP memory, and if the plugin runs into that, it fails, and there is no errors logged, because, technically, it is not an error, it is hosting imposed limit. So far, I have seen such problems on some GoDaddy, HostGator and BlueHost shared hostings, and there is nothing I can do to remedy that, that is hosting imposed limit that there is no way getting around.