This probably isn’t the ideal venue to offer this sort of support, but after investigating the issue, I can’t see why crons aren’t running beacuse I don’t have access to apache server logs.
As to the problem of JS issue, this is a server-side problem blocking requests that contain certain keywords - far beyond the control of Shield, though I’ve built a workaround for the next release so it should work regardless.
To ascertain the root cause of the problem of automated scans not running, I’d need a site that is demonstrating the issue +
- wp admin access
- ftp access
- access to full server logs (as in all likelihood the server is generating errors which can’t be seen on the webhost account).
I would welcome anyone who’s having problems with automated scans not running to try another webhost provider to see if it’s working there. I believe this to be server/webhost configuration problem (which is why I’d need access to apache server logs).