Quick answer
A cPanel cron job runs an authorized command on a schedule. Check existing jobs first so the same application task does not run twice.
Applies to
For an Interactive Online account with cron support and permission to run the documented application command. The original tutorial shows an older cPanel interface.
Steps
- Identify the application's documented command, absolute paths, correct PHP/runtime, server time zone and required frequency. Preserve existing scheduler entries.
- Open Advanced > Cron Jobs, review Current Cron Jobs and confirm that the task is not already covered by another scheduler. Configure a useful notification destination without embedding secrets in the command.
- Add only the intended schedule/command, then observe one controlled run and inspect the application's result or job log. Use supported overlap protection for a long-running job.
Check the result
Confirm the task ran once at the intended time and did not duplicate messages, payments or external requests.
Troubleshooting and support
For a failure, compare runtime paths, working directory, permissions, environment and time zone. Do not schedule rapid retries against a live transaction or paid API until its previous outcome is known.
Contact support from the owning account with the domain, product/version, exact error, time/time zone and redacted evidence. Exclude credentials, session URLs, payment details and private customer records. Confirm any separate application-support scope.
Video tutorial
The original video is retained. Its interface can differ from the current written guidance.
Related help
- Add a scheduled website task without creating duplicate jobs
- Use website error logs to diagnose a failed request
Official references
Written guidance reviewed November 1, 2026. The preserved historical tutorial has not been recertified for current software.
