Cron jobs run approved account commands on a schedule. They are useful for application maintenance, regular imports, notifications and other tasks that should happen without someone manually opening a website. Our Account Manager provides cron controls for supported accounts, including viewing schedules, creating or editing jobs and managing notification email. The command still runs within your hosting account's permissions and resource limits.
IN THIS ARTICLE
01 Prepare the command and choose a suitable schedule
Before creating a job, consult the application's instructions and identify the correct executable, script location and required schedule. Scheduled commands can run in a different environment from an interactive terminal session, so use the appropriate full paths and do not assume that the current folder or runtime will be the same. Keep the command limited to the intended task and avoid placing secret values directly in a command if a supported private configuration method is available.
Check the hosting server's configured cron timezone when choosing the run time. It may differ from the timezone displayed by your computer or your application. Choose a frequency that matches the business need, and allow enough time for one run to finish before the next starts. An import that takes several minutes should not be scheduled to overlap repeatedly without appropriate application safeguards.
02 Verify the result and avoid duplicate processing
- After saving, confirm that the job appears with the intended schedule and check its first result.
- Use the available notification or application logging to identify failures rather than assuming the task succeeded because it was scheduled.
- Avoid suppressing all useful error information until the job is working reliably.
- When replacing an existing job, check for duplicates so that messages, invoices or imports are not processed twice.
If you request help, provide the task's purpose, schedule and redacted error output, with any sensitive command arguments removed.
03 Example: create an hourly application task
If the application's instructions call for a task once per hour, open the cron controls for the intended hosting service and choose the action to add a job. Check first that this task is not already scheduled. Enter the application's actual executable and script command in the command field.
For a standard five-field cron schedule, 0 * * * * runs at minute zero of every hour in the cron scheduler's timezone:
| Schedule field | Value |
|---|---|
| Minute | 0 |
| Hour | * |
| Day of month | * |
| Month | * |
| Day of week | * |
Save once, confirm the displayed command and schedule, then check the first run's application log and expected result. This example supplies the timing only; use the command and frequency required by your application.
How do I know a cron job actually completed?
- Use the executable and script paths required by the application, and check the server cron timezone.
- Set a schedule that allows one run to finish before another begins, using application locking where needed.
- Review the first result through its log or notification, then check that the expected records or files were produced.
Avoid adding a second schedule before checking whether the application or installer already created one. Duplicate jobs can send messages or process imports twice. Keep useful error reporting enabled while diagnosing a job, and redact secret command arguments before sending output to support.