Is there such a thing as too many cron jobs and if so how many is too many? I have a bunch of domains which have cron jobs but I've noticed they don't always run. For instance, I have a new site with 50,000 Wordpress posts in draft status and a plugin which is supposed to change that status to publish for 1 post every 5 minutes but it is only publishing a new post every 60-90 minutes. Similarly, in the past I have added new cron jobs only to not see them start running for hours. It appears that the cron job for running the WP cron file is not running every 5 minutes.
Actual cron jobs in cPanel which are supposed to load the wp-cron file using wget and/or curl. I setup the same cron job using Easycron and it works fine. This happens a lot which is why most of my cron jobs are done using Easycron. Unfortunately, cron jobs that need to be done more often than 20 minutes still need to be done in cPanel due to Easycron requiring a subscription to do them more often.
I shouldn't have had to use Easycron in the first place but I learned a couple years ago that if I add 20 plus cron jobs to an account eventually the new ones don't run.
Last edited:
| Thread starter | Similar threads | Forum | Replies | Date |
|---|---|---|---|---|
| P | Too Many Connections in phpMyAdmin and Sites Offline | Databases | 5 | |
| X | Website Using Too Many Resources | Databases | 6 | |
| R | MySQLi - Too Many Connections Error due to Amazon AWS | Databases | 5 | |
|
Too Many Open Files - MariaDB | Databases | 1 | |
| R | Need to clean up , too many databases | Databases | 3 |