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 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 > 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 > System Settings > 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 > 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
| Scope | Price |
|---|---|
| Diagnosis and repair for one install, the catch-up plan and monitoring | From $99 |
| A failing task caused by a custom hook or third-party module | $65/hour or a fixed quote |
| Server-level changes that need root, such as installing a PHP version or ionCube Loader | Quoted after the call |
| Someone watching the cron and Module Queue every month | Monthly 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 or a module quote
- Email that WHMCS sends but customers never receive, which is email deliverability
- Ongoing monitoring after handover, which monthly maintenance includes
If customers are already asking where their invoices are, put that in your first message to us at contact, and the catch-up gets planned before anything else.