| docs

Appearance

Cron Jobs ​

The Cron Jobs section in AdminBolt allows users to manage scheduled tasks that execute commands at specific intervals. This is especially useful for automating scripts, updates, or repetitive server-side operations.

Note: The Cron Jobs item appears in the client menu only when your hosting plan includes Cron Jobs, your hosting account has SSH access enabled, and the server either runs CloudLinux or has SecureBox installed. If you do not see Cron Jobs in the menu, ask your hosting provider to add Cron Jobs to your plan, to enable SSH access for your account, or to confirm that the server meets these requirements.

Overview ​

Open it from Advanced > Cron Jobs. The list shows each job's Schedule and Command, with Edit and Delete on its row. If no jobs exist, a message saying "No Cron Jobs" is shown in the center.

Create Cron Job ​

Click Create Cron Job at the top-right corner to add a new task. The form has two sections:

  • Schedule - Common Settings offers ready-made schedules, from Once Per Minute to Once Per Month, and fills in Cron Expression, which you can also type yourself. Next Run Times lists when the job will run next, so you can check the expression before saving.
  • Command - Common Commands pre-fills Command to Execute with Run PHP Script or Call Webhook, or leaves it to you with Custom Command.... Edit the pre-filled command before saving.

Since panel 1.9.2, Run PHP Script fits your account: it runs script.php in your home folder with the PHP version of your account's main domain. On a CloudLinux server it uses plain php, which runs your account's own PHP version. Replace script.php with the path of your script.

Edit on a job's row opens the same form with the job's current values.

Search Feature ​

A search bar is available to filter cron jobs by keyword. This helps when managing large numbers of tasks.

No Cron Jobs ​

When no jobs are defined, the interface will show a centered message:

No Cron Jobs

This is a visual indicator that the cron table is currently empty.

Cron email ​

Cron mails the output of every job that prints something. Cron email in the header decides where those mails go:

  • Me (the account owner, system default) - the mails arrive at your account's own address.
  • Nobody (turn cron emails off) - the output is discarded.
  • A custom address - the mails go to the address you enter in Email address.

The choice applies to every cron job of your account and takes effect at once. A job that prints nothing sends no mail either way.

Cron email over the API ​

Since panel 1.9.4, GET /api/client/cron-jobs/email on the client REST API reads this choice and PUT changes it. mode is default (the account owner), off (nobody), or custom, which needs email. The choice is stored only once the server has applied it, as in the dialog. Like the other cron job endpoints, these are refused while the account has no SSH access; see API Keys.

Notes ​

  • Cron jobs created here are user-level and isolated per account.
  • On CloudLinux servers, cron commands run inside your account's CageFS environment, so each job is isolated from other accounts on the server.
  • The system uses standard crontab syntax behind the scenes.
  • A cron job restored from a backup outside the panel, for example by a JetBackup restore, is picked up and listed here within a few minutes and keeps running in the meantime. Lines the panel cannot represent, such as @reboot entries or environment assignments, are left untouched and stay outside the list.
  • A job that prints something has its output mailed as set under Cron email.