LifterLMS Certificate Not Working? Fixing Awards, Blanks and Exports
Why LifterLMS certificates are not awarded, show blank names or stale details, or print and export badly, and how to fix each case: engagement…
Read articleDelayed 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.
LifterLMS uses two scheduling systems, and both depend on WP-Cron.
wp-cron.php. No visitors means no cron.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.
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.
| Job | Hook | Scheduler |
|---|---|---|
| Recurring payment charges | llms_charge_recurring_payment | Action Scheduler |
| Upcoming payment reminder emails | llms_send_upcoming_payment_reminder_notification | Action Scheduler |
| Access plan expiration | llms_access_plan_expiration | Action Scheduler |
| Delayed engagements (email, certificate, achievement with an Engagement Delay) | lifterlms_engagement_send_email, lifterlms_engagement_award_certificate, lifterlms_engagement_award_achievement | Action Scheduler |
| Sending queued notifications | llms_dispatch_notification_processor_async | Action Scheduler |
| REST API webhook deliveries | lifterlms_rest_deliver_webhook_async (group llms-webhooks) | Action Scheduler |
| Course reporting data (averages, enrollments) | llms_calculate_course_data | WP-Cron |
| Bulk enrolling a membership's members into a course | llms_membership_bulk_enroll | WP-Cron |
| Session clean-up, log backups, temporary file clean-up | llms_delete_expired_session_data, llms_backup_logs, llms_cleanup_tmp | WP-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.
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.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.
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.
define( 'DISABLE_WP_CRON', true );
Add this to wp-config.php only after the server job in step 2 is in place.
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.
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.
wp-cron.php or admin-ajax.php. Some firewall rule sets block requests from the server to itself.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.
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.
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.
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.
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.
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.
Why LifterLMS certificates are not awarded, show blank names or stale details, or print and export badly, and how to fix each case: engagement…
Read article
A troubleshooting guide for LifterLMS quizzes that will not start, lose answers, time out, run out of attempts or grade in surprising ways, with the…
Read article
Which PHP version LifterLMS needs, which one you should actually run, and a step-by-step way to upgrade PHP on a course site without breaking…
Read articleSkip the trial and error. Get specialist LifterLMS help and ship faster.