Quick answer
A cron job runs a command on a schedule. Before adding one, confirm that the application does not already run the task through another scheduler. Duplicate jobs can send repeated messages, process orders twice, or create unnecessary load.
Before you start
You need an authorized account with cron support, the application's documented command, the correct executable and absolute paths, and an agreed schedule. Check the server time zone and resource limits.
What to do
- Inventory existing jobs and the application's own scheduler. Identify which system is intended to be authoritative.
- Test the documented command safely in the appropriate environment, using the correct PHP or other runtime and working directory.
- Add the smallest necessary schedule and configure useful error reporting. Avoid putting passwords or tokens directly into the visible command line.
- Observe one run and record its time, outcome, and effect on the application. Use locking or the application's supported overlap protection for longer tasks.
Check the result
Check the application's job receipt or log, not just the presence of a cron entry. Confirm that mail, orders, and external API actions were not duplicated.
If something does not work
If the job fails, compare runtime paths, environment variables, permissions, and time zone. Do not schedule rapid retries against a paid API or live transaction until the cause is understood.
Related help
- How to setup a cron job in cPanel
- Use website error logs to diagnose a failed request
- Check that website integrations continue to work
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
