Skip to content

Cron Jobs

Schedule recurring tasks for your hosting account.

1Overview

Cron Jobs runs account-scoped commands on a schedule, for example application maintenance or periodic imports.

Cron Jobs in the user panel. Account names, domains, and addresses are examples. Available controls depend on your package and server configuration.
User Cron Jobs page with schedule and command fields, an add job button, and the account scheduled jobs list.

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

2Before you begin

User-panel actions affect only resources owned by the signed-in hosting account. This is an advanced task; schedule it carefully and keep a rollback path.

3Step-by-step workflow

Open Cron Jobs, add a job, choose the schedule, use an absolute path inside your account or an approved runtime command, save, then check output or logs after the first scheduled run.

  1. Open Cron Jobs and review existing schedules to avoid duplicates.
  2. Prepare the exact command using absolute paths and test it in the hosting account.
  3. Choose Add Job and enter a clear description if the form offers one.
  4. Choose a schedule and confirm the time zone used by the server.
  5. Enter the command and a protected output destination when needed, then save.
  6. To change a saved job, use its Edit action, update the schedule or command, and save the edited entry.
  7. Check that the edited job appears once with the correct command and schedule.
  8. Review its first scheduled run and remove obsolete jobs when no longer required.

4Practical example

Example: a job that should run once each hour can use 0 * * * *. Confirm the panel schedule preview and server time zone before relying on an exact local time.

5Reading a basic cron schedule

The five fields describe minute, hour, day of month, month, and day of week. An asterisk means every allowed value. For example, 0 2 * * * runs at 02:00 each day in the scheduler time zone. Use a simple schedule and verify the next run if the panel displays it.

Keep frequent jobs short enough to finish before the next run or use the application locking mechanism. Do not put passwords directly in a command; use the application configuration or the provider approved secret mechanism.

6Verify the result

Validate the outcome from the affected website, mailbox, application, or client connection after the panel reports success.

  1. Confirm the job displays the expected schedule and command.
  2. Review its first execution result or output log.

7Common problems and what to check

The job never runs: check its schedule, absolute executable path, working directory, and permissions.

The job runs twice: review duplicate entries and application-level schedulers.

It works manually but fails on schedule: the scheduled environment may have a different PATH or missing environment settings.

8Security, impact, and rollback

Prevent overlapping jobs and avoid placing passwords or API tokens in the command line. Use a script with protected permissions when a secret is needed.

Related guides

LogsRead website and application error evidence.TerminalRun account-scoped commands in the hosting environment.See all guides in User hosting panel

Still need a hand?

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

Open client area