Members CMS
PHP 8.1+ & MySQL Buy license · $349.95
Hosting & security

Why scheduled releases need a cron job, not page visits

Releases triggered by visitors run late, twice or not at all. How a server cron job, locking and missed-release policies keep a drip schedule reliable.

Updated 4 minute read The Members CMS team

A content drip schedule is a promise to your members: five new sets every two days at 09:00, a new video every week, a new story every three days. Keeping that promise depends on something running the release at the right moment. On many websites that "something" is simply the next visitor to load a page, and that is where schedules start going wrong.

This guide explains why visitor-triggered releases are unreliable, what a cron job is, and how locking and missed-release policies keep a drip schedule on time even when things go wrong.

The problem with page-visit triggers

Some systems check for due tasks whenever someone visits the site. If a release was due at 09:00 and nobody visits until 09:47, the release happens at 09:47. That might seem harmless, but it causes real problems:

  • Late releases. A quiet site may not get a visitor for hours, especially overnight.
  • Double releases. Two visitors arriving at the same moment can both start the same release.
  • Slow pages. The unlucky visitor waits while the release runs.
  • Missed releases. If the task fails part way, nothing tries again until the next visit, and maybe not even then.

For a central library feeding several sites, page visits are an even poorer trigger, because the CMS itself may not be visited at all for days.

What a cron job is

A cron job is a task the server runs automatically at set times, whether anyone is visiting or not. It is a standard feature of Linux servers. You tell the server what to run and how often, for example every minute, and it just does it.

A typical setup runs one small command every minute. That command checks whether any release is due and, if so, runs it. Running every minute means releases happen within a minute of their scheduled time.

Adding one in a control panel

You don't need to use the command line. Hosting control panels such as cPanel have a Cron Jobs page where you:

  1. Choose how often it runs (every minute is common for schedulers).
  2. Paste in the command the software gives you.
  3. Save it, then check the software reports that the scheduler is running.

If your host doesn't allow cron jobs, or only allows them every hour or so, ask before you buy. Our guide on what you need to self-host a content CMS lists this alongside the other questions to ask.

Preventing double releases with locking

Even with cron, a release could overlap with itself. If a large release takes longer than a minute, the next cron run could start before the first finishes. Locking prevents this.

When a release starts, it places a lock saying "this release is in progress". Any other run that finds the lock leaves it alone. When the release finishes, it is recorded as done, so a later run sees it is complete and does nothing. This is sometimes called idempotency: running the same job twice has the same effect as running it once.

Locking also matters around daylight saving changes, when an hour is repeated in autumn. Our guide on scheduling across time zones and daylight saving covers how releases avoid running twice in that hour.

What happens after downtime

Servers sometimes go down for maintenance or because of a fault. When they come back, some releases may have been missed. A missed-release policy decides what happens next.

PolicyWhat it doesGood for
Run latest missedRuns only the most recent missed releaseKeeping to schedule without a sudden flood
Catch up within a limitRuns missed releases, up to a set numberMaking sure members get everything they were promised
SkipIgnores missed releases and waits for the next oneSites where timing matters more than quantity

For example, if Puppy Obedience Club releases 5 image sets every 2 days and the server was down for 5 days, "run latest missed" releases one batch, "catch up" might release two or three batches, and "skip" releases none until the next due date. Whatever you choose, remember that releases draw on your stock, so catching up uses content faster. Our guide on content reserves explains how to keep enough back.

Keeping an eye on the scheduler

  • Check that the scheduler reports a recent run.
  • Look at the release history for failed or late releases.
  • Retry failed releases once the cause is fixed.
  • Make sure one site's failure doesn't hold up the others.

It also helps if the scheduler does other routine work, such as generating thumbnails, retrying failed jobs and running backups, through the same cron job. One job that runs every minute and works through a queue is easier to check than several separate tasks, and if it stops, you notice straight away because everything waits.

How Members CMS handles this

Members CMS runs every scheduled release from a server cron job, never from page visits. Releases are locked while they run and recorded once, so a release never runs twice, and times are stored in UTC and planned in each site's own time zone.

Under Content Drip you'll find Upcoming Releases, the Release Queue, Release History and Failed Releases, with pause, resume, retry and manual releases. You choose the missed-release policy (run latest missed, catch up within a limit, or skip), and one site failing never blocks the others. Once a release runs, the new content appears in each website's members area and tour through the connector.

The same cron job also handles background processing such as thumbnails and scheduled backups. Without cron, processing can still run while an administrator has the admin area open, but drip schedules and timed offer expiry need the cron job, so add it before you switch any schedule on.

Frequently asked questions

What is a cron job?

A task the server runs automatically at set times, such as every minute. Hosting control panels like cPanel let you add one without using the command line.

What if the server was down when a release was due?

A missed-release policy decides: run only the latest missed release, catch up missed releases within a limit, or skip them.

How are duplicate releases prevented?

Each release is locked while it runs and recorded once, so a second copy of the job finds it already done instead of releasing the content twice.

Get three guides like this every month, plus software update notices.Subscribe →