The WHMCS system cron performs due automation tasks such as invoicing, payment processing and account actions. Configure it on the server that owns the live installation, using the PHP command appropriate to the installed WHMCS release.
IN THIS ARTICLE
01 Install the correct scheduled command
- Open Automation Settings in WHMCS and locate the recommended cron command for this installation. Check the PHP binary and path to
cron.php. - If the cron directory was moved outside the public web directory, confirm its configuration points back to the installation and that the WHMCS configuration identifies the moved cron directory.
- Create a cron entry under the intended hosting account or application user. WHMCS recommends running the system cron every five minutes so that tasks become eligible promptly.
- Configure the daily Time of Day setting separately in Automation Settings. The frequent scheduler invocation does not mean every daily task runs every five minutes.
- Allow the next scheduled execution, then check Automation Status and the relevant logs for successful activity.
A generic schedule resembles */5 * * * * /path/to/php -q /private/crons/cron.php. Both paths are placeholders and must be replaced with the actual PHP executable and cron file. Use the command generated or verified for your installation.
How do I avoid duplicate WHMCS cron execution?
Check the hosting panel, operating-system scheduler and any external scheduling service before adding another entry. During migration, keep the old server's cron disabled once the destination becomes active. Repeated cron installations make troubleshooting harder even when WHMCS prevents some overlapping work.
POP email import uses its own process when configured. Add it only when your support-mail design uses importing, and avoid delivering the same mailbox through both importing and piping.
02 Confirm the execution environment
The command-line PHP version can differ from the website's PHP version. Compare versions, extensions and configuration files if the client area works but automation fails. WHMCS 9.0 restricts HTTP cron access, so use the documented command-line process wherever available instead of exposing a public cron URL.