Before you start
You need write permission for the website and a command that is safe to run on its intended data. Know its directory, resource needs, repetition behaviour and recovery path.
What to do
- Open the website's Cron jobs tab and check existing jobs before using Add cron job.
- Enter a name, command and working directory relative to /site. Set the five-field UTC expression in minute, hour, day, month and weekday order; for example, 0 3 * * * means daily at 03:00 UTC.
- Review the maximum runtime, memory, CPU and environment settings before saving. Reopen the saved job and check its Scheduled or Paused state.
- Use Run now only when an immediate execution is intended. Inspect Logs and the actual outcome before starting another execution.
- Use Pause or Enable to control future scheduling. Use Edit for configuration changes, and check the accepted state afterwards.
- Use Remove only for the intended schedule. Its confirmation states that the managed schedule is removed and application files are retained.
What happens next
The accepted website schedule and its current enabled state can be inspected separately from an individual run's output. A saved schedule is not proof that its command has completed successfully.
If something goes wrong
Recheck UTC conversion, expression fields, directory, command permissions, runtime limits and logs if a run is missing or fails. Pausing future runs is not proof that existing work has stopped. After a timeout or uncertain response, inspect current execution state before retrying, especially for imports, messages or other work that must not be duplicated. Contact the infrastructure administrator with the job name and time, without secrets.
