Great! The first area to check is the /var/log/cron file to confirm that the cron in question is running properly. If not, I would hope that log has additional details about the error with the cron not running at all.
Yes I ran, grep CRON /var/log/cron
Aug 29 19:15:01 vmi1331732 CROND[30688]: (root) CMD (/usr/local/cpanel/scripts/dcpumon-wrapper >/dev/null 2>&1)
Aug 29 19:16:01 vmi1331732 CROND[30726]: (magcrm) CMD (wget
https://x.x.x.x/crm/vtigercron.php)
Aug 29 19:16:01 vmi1331732 CROND[30727]: (root) CMD (/usr/sbin/imunify-notifier -update-cron)
Aug 29 19:17:01 vmi1331732 CROND[30836]: (magcrm) CMD (wget
https://x.x.x.x/crm/vtigercron.php)
Aug 29 19:17:01 vmi1331732 CROND[30837]: (root) CMD (/usr/sbin/imunify-notifier -update-cron)
Aug 29 19:18:01 vmi1331732 CROND[30869]: (root) CMD (/usr/sbin/imunify-notifier -update-cron)
Aug 29 19:18:01 vmi1331732 CROND[30870]: (magcrm) CMD (wget
https://x.x.x.x/crm/vtigercron.php)
Aug 29 19:19:01 vmi1331732 CROND[30907]: (root) CMD (/usr/sbin/imunify-notifier -update-cron)
Aug 29 19:19:01 vmi1331732 CROND[30913]: (magcrm) CMD (wget
https://x.x.x.x/crm/vtigercron.php)
Aug 29 19:20:01 vmi1331732 CROND[30939]: (root) CMD (/usr/local/cpanel/scripts/dcpumon-wrapper >/dev/null 2>&1)
Aug 29 19:20:01 vmi1331732 CROND[30940]: (root) CMD (/usr/local/cpanel/scripts/eximstats_spam_check 2>&1)
Aug 29 19:20:01 vmi1331732 CROND[30941]: (root) CMD (/usr/lib64/sa/sa1 1 1)
Aug 29 19:20:01 vmi1331732 CROND[30943]: (root) CMD (/usr/sbin/imunify-notifier -update-cron)
Aug 29 19:20:01 vmi1331732 CROND[30944]: (magcrm) CMD (wget
https://x.x.x.x/crm/vtigercron.php)
Aug 29 19:20:01 vmi1331732 CROND[30945]: (root) CMD ( imunify360-agent malware on-demand check-detached > /dev/null 2>&1 ||

Aug 29 19:21:01 vmi1331732 CROND[31040]: (root) CMD (/usr/sbin/imunify-notifier -update-cron)
Aug 29 19:21:01 vmi1331732 CROND[31041]: (magcrm) CMD (wget
https://x.x.x.x/crm/vtigercron.php)
......... and more