# WHMCS Cron Job Fixing

> WHMCS cron repaired on your server, plus a safe catch-up so customers are not suspended over invoices they never got.

WHMCS cron not running? We diagnose and repair it on your server, plan the catch-up of missed invoices, fees and suspensions with you, and set up monitoring.

- **Price:** Starting at $99
- **Billing:** One-time, fixed scope
- **Category:** WHMCS
- **Quote turnaround:** Fixed-price quote within 24 hours
- **Start a project:** https://whmcspilot.com/start-project
- **Details:** https://whmcspilot.com/services/whmcs-cron-fixing
- **Last updated:** 2026-11-05

## Overview

Our WHMCS cron fixing service is for owners whose invoices, reminders, suspensions or provisioning have stopped and who want someone else to find the cause and get automation running again. It is a fixed-price job from $99 per install. If you would rather work through it yourself, our guide to [a WHMCS cron that is not running](/blog/whmcs-cron-not-running) lists the usual causes and how to test for them; this page describes what we take care of when you hand the problem to us, including the clean-up a guide cannot do for you.

## What we do on your server

- Read Utilities &gt; Automation Status, System Health and the Activity Log to see when the cron last completed and which tasks failed
- Check the cron entry itself: schedule, system user, the PHP binary it calls and the path to crons/cron.php, against the command shown in Automation Settings
- Run the cron by hand as the account that owns WHMCS with verbose output, which shows the real error a scheduled run hides
- Correct whatever is broken, whether that is the command, the PHP version, ionCube Loader, memory or time limits, permissions, a moved crons directory or an HTTP-triggered job that WHMCS 9.x now blocks
- Trace failing tasks inside a run, such as a dead server under Configuration &gt; System Settings &gt; Servers or a registrar module with expired credentials
- Look for custom hooks on the AfterCronJob or DailyCronJob points, since one uncaught error there can halt the run
- Check crons/pop.php or email piping if support mail arrives through them

## The catch-up after a long outage

This is where a do-it-yourself fix most often goes wrong. When the cron has been down for days or weeks, the first successful daily run does everything that has been waiting at once: it creates invoices for services that came due during the outage, applies late fees, sends overdue reminders, attempts card captures, suspends overdue services, terminates the ones past your termination days and cancels old unpaid invoices. A customer who never received an invoice can be invoiced, charged a late fee and suspended within the same hour.

Before the first full run, we list what is due and agree the order with you. Typical choices:

- Run invoice creation and reminders first, and hold back AutoSuspensions, AutoTerminations and AddLateFees for a few days using the cron's skip argument
- Waive or remove late fees on invoices that were generated late
- Push back due dates for clients who were never sent an invoice
- Retry or clear the failed actions waiting in Utilities &gt; Module Queue

Once customers have had time to pay, the held tasks go back into the normal five-minute schedule.

## Keeping it fixed

- A cron email address set while we test, then quieted once the job runs cleanly
- A check that the admins who should receive WHMCS's own cron warning emails actually do
- An optional heartbeat, where each run pings an outside monitor such as Healthchecks.io and you are alerted when the pings stop
- A short written record of the final cron command, which user's crontab holds it and which PHP binary it uses

## What we need from you

- cPanel, Plesk or DirectAdmin access, or SSH as the account that owns WHMCS
- A WHMCS admin login
- The date things stopped, if you know it
- Your preference on late fees and suspensions for the catch-up

## Scope and price

ScopePriceDiagnosis and repair for one install, the catch-up plan and monitoringFrom $99A failing task caused by a custom hook or third-party module$65/hour or a fixed quoteServer-level changes that need root, such as installing a PHP version or ionCube LoaderQuoted after the callSomeone watching the cron and Module Queue every monthMonthly maintenance, $199/month

Billing is 50% at approval and 50% once automation runs again, and if the repair fails within 14 days we put it right at no charge.

## What sits outside this job

- Rewriting a broken custom module, which is hourly [bug fixing](/services/whmcs-bug-fixing) or a module quote
- Email that WHMCS sends but customers never receive, which is [email deliverability](/services/whmcs-email-deliverability)
- Ongoing monitoring after handover, which [monthly maintenance](/services/whmcs-monthly-support) includes

If customers are already asking where their invoices are, put that in your first message to us at [contact](/contact), and the catch-up gets planned before anything else.

## What's included

- Automation Status, System Health and Activity Log reviewed
- Cron schedule, user, PHP binary and path checked against Automation Settings
- Manual verbose run as the account that owns WHMCS
- Command, PHP, ionCube, limits, permissions or crons directory corrected
- Failing tasks traced to dead servers, registrar modules or hooks
- Catch-up plan for missed invoices, late fees, suspensions and terminations
- Held tasks run later with the cron's skip argument
- Module Queue retried or cleared
- Optional heartbeat monitor that alerts you when runs stop
- Written record of the final cron command and where it lives

## Business outcomes

- Invoicing, reminders and provisioning run on schedule again
- Customers are not hit with late fees and suspensions for an outage that was not their fault
- You hear about the next failure from a monitor, not from a customer
- The written record means anyone can check the cron later
- Fixed price from $99, with hourly work only if custom code is to blame

## Frequently asked questions

### How much does it cost to fix the WHMCS cron?

From $99 per install for diagnosis, repair, the catch-up plan and monitoring. If a custom hook or module causes the failure, that part costs $65 per hour or gets its own quote.

### What happens when the cron restarts after weeks off?

The first daily run processes everything that is due, including invoices, late fees, suspensions and terminations. We plan that run with you so customers are not penalized for the outage.

### Should I just run the cron with the force option?

Not before checking what is due. A forced full run after a long outage can suspend many accounts at once, so hold back suspensions and late fees until customers have had a chance to pay.

### Do I need SSH access?

No. Control panel access to cPanel, Plesk or DirectAdmin is enough for most repairs. Installing a PHP version or ionCube Loader at server level needs root, which we quote separately.

### Why did my cron stop after upgrading to WHMCS 9?

Often because it called cron.php over HTTP, which WHMCS 9.0 and later block by default. We switch it to a command-line call with the right PHP binary.

### Can you watch the cron every month?

Yes, through the monthly maintenance plan at $199 per month, which checks cron run times and the Module Queue.
