Cron failures are usually caused by an incorrect command path, disabled script permissions, environment assumptions, or silent application-level errors inside the scheduled script.
Common symptoms
- Invoices, queues, or maintenance tasks stop processing
- Cron appears saved but nothing happens
- The script works manually but not on schedule
Troubleshooting steps
- Review the exact cron command in cPanel and verify the PHP path, script path, and any required flags are correct.
- Run the command manually where possible to see whether it prints an error.
- Confirm the target script is readable and executable in the expected context.
- Check application logs for exceptions that occur when the cron launches.
- Avoid overly frequent schedules that overlap previous runs.
Additional notes
- A cron can execute successfully from the scheduler but still fail inside the application.
- Relative paths that work in a browser often fail in cron context.
When to contact support
Contact support if the cron command is correct but still never triggers.