\u201cWhat the heck is a cron?\u201d I field this question at least once a month from non-developers. It\u2019s a great question. I\u2019m going to break it into two questions though.<\/p>\n\n\n\n
\u201cWhat is a CRON?\u201d
\u201cWhat is WP-CRON?\u201d<\/p>\n\n\n\n
At its heart, a cron is a \u201ctime-based scheduler\u201d. It handles tasks that need to be done on a regular basis and at a specific time. As an example, if you want your WordPress blog to display the weather forecast in the header, then each morning you need to go get the weather forecast. Yes, you could hire someone to log in each morning, go get the forecast and paste it into a widget. <\/p>\n\n\n\n
A better plan is to have a program that runs each morning and talks to an API to fetch the day\u2019s forecast and update your database for you. The program that runs your weather fetching program is called a CRON. The name is derived from \u201cchronological\u201d which roughly translates into \u201cin order of time\u201d. <\/p>\n\n\n\n
Most systems these days have some concept of a cron. Unix based systems (Unix, Linux, macOS, etc.) actually have a version of a traditional cron. While some might put a nice graphical interface on them, they all boil down to a program named cron and a file named crontab. <\/p>\n\n\n\n
The program cron is always running in the background and every minute it looks at the crontab and figures out if something needs to be done. If not, it goes back to sleep. <\/p>\n\n\n\n
The crontab file contains when a program should be run and which program should be run. Each line represents a different task. They look something like this.<\/p>\n\n\n\n
1 0 * * * ~\/fetchForcast.sh<\/pre>\n\n\n\nWhile this may look cryptic, all it is telling cron is that at 12:01 AM every day, run a program called fetchForcast.sh. Note that time added in the Cron tool is in UTC by default. Here is an easy guide to reading a crontab.<\/p>\n\n\n
# \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500 minute (0 – 59)
# \u2502 \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500 hour (0 – 23)
# \u2502 \u2502 \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500 day of the month (1 – 31)
# \u2502 \u2502 \u2502 \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500 month (1 – 12)
# \u2502 \u2502 \u2502 \u2502 \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500 day of the week (0 – 6) (Sunday to Saturday;
# \u2502 \u2502 \u2502 \u2502 \u2502 7 is also Sunday on some systems)
# \u2502 \u2502 \u2502 \u2502 \u2502
# \u2502 \u2502 \u2502 \u2502 \u2502
# * * * * *
1 0 * * * ~\/fetchForcast.sh<\/p>\n\n\nNow that you have the key, it\u2019s pretty easy, huh? <\/p>\n\n\n\n
That really is all there is to a traditional cron. Most hosts like SiteGround allow you access to the cron for your system. Sometimes you have to edit the crontab manually, but many hosts have a much better interface for you to use. Either way, you have the ability to run programs at a specific time and on a regular basis.<\/p>\n\n\n\n
<\/span>What is WP-CRON<\/span><\/h2>\n\n\n\n
Like most things, WordPress does things just a little differently. Because many plugin authors needed to be able to schedule things to happen regularly, and because many WordPress site owners don\u2019t know where their crontab is, much less how to edit it, WordPress re-invented the cron.<\/p>\n\n\n\n
At its core, WP-CRON acts like a traditional cron in that a developer can \u201cschedule\u201d a task to be done on a regular basis. However, unlike a traditional cron, WordPress does not have a program that is always running in the background of your server. So to make this world, WP-CRON is a process that is called every time a page is viewed. <\/p>\n\n\n\n
On busy sites, this works fine. However, if your site isn\u2019t busy, a task scheduled for 2:00 AM might be run at 5:24 AM if nobody visits your site until then. Sometimes this is ok, other times this is a problem.<\/p>\n\n\n\n
If the tasks you need to run are time-sensitive and have to be run at the time scheduled, WP-CRON is not the scheduler you want to use. If on the other hand, the tasks you need to be done can happen \u201caround\u201d the time you schedule them, then WP-CRON is fine. Again, a lot depends on how busy your site is.<\/p>\n\n\n\n
<\/span>What are the alternatives?<\/span><\/h2>\n\n\n\n
If you have tasks that are time-sensitive and your host does not allow you access to the system\u2019s cron, you have 2 alternatives. First, you can switch to a host like SiteGround that gives you this access. If that\u2019s not possible, then there are several services free or paid that are nothing more than cron services. <\/p>\n\n\n\n