LifterLMS Cron Problems: Fix Late Emails, Renewals and Engagements

Which LifterLMS jobs depend on WP-Cron and the Action Scheduler, how to tell whether your scheduler is broken, and how to replace unreliable WP-Cron with a real server cron job.

  • Add as a preferred source on Google
Illustration for “LifterLMS Cron Problems: Fix Late Emails, Renewals and Engagements”

Delayed emails that never arrive, certificates that appear days late, renewals that were never charged and reports that never update usually have one thing in common: the site's scheduler is not running on time. LifterLMS hands a lot of its work to background jobs, and those jobs only run when WordPress's scheduler wakes up.

This guide is for site owners and developers who suspect a LifterLMS cron problem. You will learn which LifterLMS features depend on scheduling, how to prove whether the scheduler is the cause, and how to set up cron so it runs reliably.

If your specific symptom is missing emails or failed renewals, our focused guides on LifterLMS emails not sending and recurring payments not processing go deeper on those. This article covers the scheduler underneath both.

How scheduling works in LifterLMS

LifterLMS uses two scheduling systems, and both depend on WP-Cron.

  • WP-Cron is WordPress's built-in scheduler. It is not a real clock. On each page request, WordPress checks whether any scheduled event is due and, if so, fires a background request to wp-cron.php. No visitors means no cron.
  • Action Scheduler is a job queue library that ships inside LifterLMS (version 3.5.4 in LifterLMS 10.3). It stores jobs in its own database tables and processes them in batches. Its queue runner is started by WP-Cron, and it can also start itself through asynchronous requests from the admin. You can see its queue under LifterLMS > Status > Scheduled Actions.

LifterLMS also runs a few background processors that work through queued batches using a request back to the site itself (a loopback request) with a WP-Cron health check as the fallback. If loopback requests are blocked, those batches wait for cron instead.

Which LifterLMS jobs depend on cron

These are the scheduled hooks in LifterLMS core and where they live. Knowing the hook name lets you search for it in the Scheduled Actions screen or with WP-CLI.

JobHookScheduler
Recurring payment chargesllms_charge_recurring_paymentAction Scheduler
Upcoming payment reminder emailsllms_send_upcoming_payment_reminder_notificationAction Scheduler
Access plan expirationllms_access_plan_expirationAction Scheduler
Delayed engagements (email, certificate, achievement with an Engagement Delay)lifterlms_engagement_send_email, lifterlms_engagement_award_certificate, lifterlms_engagement_award_achievementAction Scheduler
Sending queued notificationsllms_dispatch_notification_processor_asyncAction Scheduler
REST API webhook deliverieslifterlms_rest_deliver_webhook_async (group llms-webhooks)Action Scheduler
Course reporting data (averages, enrollments)llms_calculate_course_dataWP-Cron
Bulk enrolling a membership's members into a coursellms_membership_bulk_enrollWP-Cron
Session clean-up, log backups, temporary file clean-upllms_delete_expired_session_data, llms_backup_logs, llms_cleanup_tmpWP-Cron

Two things are not on this list. Drip content does not use cron: whether a lesson is available is worked out from dates each time the page loads, so a broken scheduler does not keep lessons locked. And LifterLMS core has no "lesson is now available" email; if you send one, it comes from an add-on, an automation tool or custom code, and that tool has its own scheduling.

Signs your LifterLMS cron is not running

  • Engagement emails with a delay arrive in bursts, often right after you log in to the dashboard.
  • Certificates or achievements set to award after a delay never appear.
  • An order's next payment date passes with no note on the order about a charge attempt.
  • Reporting figures for a course stay the same for days.
  • You add an auto-enrollment course to a membership, ask LifterLMS to enroll the existing members, and they never appear in the course.
  • Tools > Site Health warns about a late scheduled event or a failed loopback request.

How to diagnose a LifterLMS cron problem

  1. Look at the queue. Open LifterLMS > Status > Scheduled Actions and filter by Pending. Actions whose scheduled date is well in the past mean the queue is not being processed. Then check Failed: a failed action shows the error that stopped it, which points to a code problem rather than a scheduling one.
  2. Check whether WP-Cron is disabled. The System Report tab on the same Status screen shows a WP Cron row. "No" means DISABLE_WP_CRON is set in wp-config.php, so a real server cron job must be calling wp-cron.php. If nobody set one up, nothing runs.
  3. Run Site Health. Tools > Site Health tests loopback requests and late scheduled events. A failed loopback is common behind HTTP basic authentication, some firewalls and some CDN rules.
  4. List due WP-Cron events with WP-CLI. If you have shell access:
wp cron test
wp cron event list --fields=hook,next_run_relative,recurrence
wp action-scheduler run --hooks=llms_charge_recurring_payment --batches=1

wp cron test checks that WP-Cron can spawn. The event list shows events that are overdue. The last command processes one batch of a specific Action Scheduler hook, which is a quick way to prove the jobs themselves work when they are given a chance to run.

Fix it: replace WP-Cron with a real server cron job

On any site that takes payments, do not rely on visitor traffic to run renewals. Switch to a server cron job. The approach is described in the WordPress handbook page on hooking WP-Cron into the system task scheduler.

Step 1: Stop page loads from triggering cron

define( 'DISABLE_WP_CRON', true );

Add this to wp-config.php only after the server job in step 2 is in place.

Step 2: Run cron from the server every five minutes

With WP-CLI available, a crontab entry like this is the most reliable option. Adjust the paths to your server:

*/5 * * * * cd /var/www/example.com/public && wp cron event run --due-now --quiet

Without WP-CLI, request wp-cron.php over HTTP instead:

*/5 * * * * wget -q -O - "https://example.com/wp-cron.php?doing_wp_cron" > /dev/null 2>&1

Many managed hosts have a panel option for this, and some already run a server cron for you. Ask before adding a second one.

Step 3: Give large queues their own runner

Sites with thousands of renewals or heavy engagement schedules can run the Action Scheduler queue directly, so it does not compete with other cron events:

*/5 * * * * cd /var/www/example.com/public && wp action-scheduler run --batch-size=50 --quiet

Keep batches small enough to finish well within your PHP time and memory limits. A runner that dies halfway leaves actions stuck in progress.

Common causes of a stuck queue

  • Cron disabled with no replacement. The most common one, often left behind by a migration or a performance plugin.
  • Password protection or maintenance mode. HTTP basic authentication blocks the loopback requests that start background work. Whitelist the server's own IP or use a server cron job with WP-CLI.
  • Security rules blocking wp-cron.php or admin-ajax.php. Some firewall rule sets block requests from the server to itself.
  • A staging clone. On a site LifterLMS detects as a clone, scheduled renewals still run but skip the charge. That is by design; see our staging and recurring payments guide.
  • Fatal errors in a callback. If one plugin's scheduled task crashes, the runner stops for that request. Check failed actions and the PHP error log.
  • Runaway queues. Hundreds of thousands of completed actions slow the queue down. Action Scheduler cleans up old completed actions itself, but a site that has been broken for months may need a manual clean-up and a database review.

Monitor the queue so you hear about it first

Do not wait for a student to tell you. A small must-use plugin can check once an hour for LifterLMS actions that are more than an hour overdue and email the site administrator. Save it as wp-content/mu-plugins/llmsx-queue-monitor.php:

<?php
/**
 * Plugin Name: LLMSX Queue Monitor
 */

add_action( 'init', function () {
	if ( function_exists( 'as_has_scheduled_action' ) && ! as_has_scheduled_action( 'llmsx_check_queue' ) ) {
		as_schedule_recurring_action( time() + HOUR_IN_SECONDS, HOUR_IN_SECONDS, 'llmsx_check_queue' );
	}
} );

add_action( 'llmsx_check_queue', 'llmsx_check_queue' );

function llmsx_check_queue() {
	$overdue = as_get_scheduled_actions(
		array(
			'hook'         => 'llms_charge_recurring_payment',
			'status'       => ActionScheduler_Store::STATUS_PENDING,
			'date'         => time() - HOUR_IN_SECONDS,
			'date_compare' => '<=',
			'per_page'     => 20,
		),
		'ids'
	);

	if ( $overdue ) {
		wp_mail(
			get_option( 'admin_email' ),
			'LifterLMS renewals are overdue',
			sprintf( '%d renewal actions are more than an hour late. Check LifterLMS > Status > Scheduled Actions.', count( $overdue ) )
		);
	}
}

This monitor runs through the same queue it is watching, so it cannot warn you if the queue stops entirely. For that, use an external uptime service that requests a URL on your site and alerts on failure, or a host-level cron health check.

Frequently asked questions

Does LifterLMS need a real cron job?

It works without one on busy sites, but any site with recurring payments or delayed engagements should use a server cron job. Low-traffic periods otherwise delay renewals and emails.

Is it safe to run actions manually from the Scheduled Actions screen?

Yes. The run link processes that single action as if the queue had reached it. Avoid running a renewal action twice; check the order notes first.

Why do LifterLMS emails arrive when I log in?

Your admin visit triggers WP-Cron and the Action Scheduler's admin runner, which then process everything that was waiting. That pattern is a strong sign that cron is not running on its own.

Does drip content depend on cron?

No. LifterLMS checks drip dates when the lesson loads, so lessons unlock on time even if cron is broken. Any email announcing the unlock comes from another tool.

What to do next

Open LifterLMS > Status > Scheduled Actions now and look for overdue pending actions. If you find any, check the WP Cron row in the System Report, then set up a server cron job as shown above and confirm the backlog clears.

If renewals have been missed or the queue is very large, get help before you run everything at once, so you do not charge customers twice or flood their inboxes. Our LifterLMS support team can clear the backlog safely, and our optimization service sets up cron and monitoring for high-volume sites. Contact us with a copy of your System Report.

Add LifterLMS Expert to your preferred sources

Add lifterlmsexpert.com as a preferred source on Google, or open this article in your AI assistant to use it as a source.

  • Add as a preferred source on Google
Free consultation

Prefer expert help over DIY?

Skip the trial and error. Get specialist LifterLMS help and ship faster.

Talk to a LifterLMS Expert Explore our services

Replies within one business day