Andrei
Not at all. By default, Enhance replaces native WordPress WP-Cron with its own scheduler , that’s actually a good thing and a common practice among managed WordPress hosts to improve performance. (This cron is what’s responsible for running scheduled posts and other automated tasks.)
Sometimes, though, the cron can run late or stop working. You can troubleshoot or just use the tool we built into cPFence to force-run any due cron events with:
cpfence --bulk-run-due-wp-cron
This will run all due WordPress cron jobs server-wide. You can also use the built-in WebUI tool to trigger due cron jobs cluster wide without SSH available in the WebUI >> Tools & Utilities >> WP-AutoShield Bulk Tools >> Run Due WP Cron
As for WP-AutoShield, it has a feature to disable native WP-Cron because sometimes Enhance misses a few sites when making the switch, so we added it to help ensure all our sites use Enhance’s better system.
We also run this daily cronjob on our own servers to make sure nothing is left behind and all scheduled tasks, run as expected.
0 7 * * * /opt/cpfence/app/setup/cpfmain --bulk-run-due-wp-cron -y >/dev/null 2>&1
