Skip to content

Cron Jobs

Review and manage scheduled work.

1Overview

Cron Jobs schedules commands at fixed times for server or account tasks. The panel validates supported schedule and command forms before saving.

Cron Jobs in the administrator panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.
Administrator Cron Jobs form with hosting account selection, schedule and command fields, and the saved jobs list.

Cron Jobs in the administrator panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.

2Before you begin

Administrator actions can affect multiple customer accounts and server services.

3Step-by-step workflow

Open Cron Jobs, create a descriptive job, choose the schedule, use the required absolute command path, and review the saved entry. Check logs or task output after the first run.

  1. Open Cron Jobs and select the account whose scheduled command should run.
  2. Review existing jobs so you do not schedule the same task twice.
  3. Add a job with a descriptive name, the intended schedule, and an absolute command path.
  4. Include the required working directory when the application depends on one.
  5. Save the job and check the displayed schedule and command.
  6. Use Edit for an existing job when available; review all fields before saving the replacement.
  7. Check the first scheduled execution through the application output or approved log.
  8. Remove obsolete jobs after confirming no active website or application depends on them.

4Practical example

Example: an hourly cleanup job should point to the correct account script and write its result to a protected account log. Scheduling every minute can create overlapping work if that script takes longer than a minute.

5Verify the result

Validate the outcome from the affected account or an independent client connection, not only from the administrator screen.

  1. Confirm the saved schedule and command are displayed correctly.
  2. Review output or logs after the first planned run.

6Common problems and what to check

A command works manually but not in cron: use absolute paths and explicitly supply the working directory.

No output appears: check the output destination and the server time used for the schedule.

Jobs overlap: increase the interval or add application-level locking after reviewing the script.

7Security, impact, and rollback

Avoid overlapping jobs, destructive shell commands, and secrets in command lines. A job that runs as root needs a narrow, reviewed purpose.

Related guides

BackupsCreate, inspect, and restore protected account backups.SSL/TLS certificatesIssue, inspect, renew, and remove website certificates.See all guides in Administrator panel

Still need a hand?

Get help with your plan, website, or hosting through your client area.

Open client area