How to manage cron jobs in Kiravo

Open your website in the hosting control panel, then choose Advanced → Developer tools → Cron jobs. Cron runs recurring work such as scheduled application tasks or synchronization scripts.

A website with no scheduled entries shows No cron jobs and an Add button. Check existing jobs before adding another task that does the same work.

Add a cron job

1. Click Add under Cron jobs.
2. Choose Run command or Request URL under Cron type.
3. Enter the corresponding Command or Request URL.
4. Choose Interval, using a preset or Custom as described below.
5. Review the website, command or URL, and frequency, then click Add. Use Cancel to discard the form.
6. Check that the intended job appears with the expected schedule. Confirm its result after the next scheduled run.

Run command

Use the exact command supplied for your application. Check executable and script paths against this website’s environment. Use absolute paths when needed rather than assuming the task starts in public_html or has the same environment as your interactive shell.

A command can change files, update a database, or send messages. Test it in a suitable environment before scheduling it on a live website. Avoid putting passwords or access tokens directly in a command that will be visible in the panel.

Request URL

Choose Request URL when the application provides an endpoint intended for scheduled requests. Use its complete HTTPS URL and follow its authentication requirements. A page loading in the browser does not prove that it is the correct scheduled-task endpoint.

Treat URLs containing tokens as credentials. Keep them out of public screenshots and support messages. If the endpoint sends messages or changes data, repeated requests can repeat those effects.

Set the interval

The selector currently offers Every minute, Every 15 minutes, Every hour, Every day, Every week, Every month, and Custom.

Start with the frequency required by the application. Make sure one run normally finishes before the next begins. If the application can overlap runs, use its locking or overlap controls rather than assuming cron prevents duplicates.

Custom schedules

Custom exposes five fields in this order: Minute, Hour, Day of month, Month, and Weekday.

Enter the value for each field separately. For example, a daily run at 02:00 uses 0, 2, *, *, * in that order. An asterisk allows every value for that field. See the cron field reference for ranges and step syntax.

Confirm the scheduler’s time zone with support if the task must run at a specific local time. Do not assume it follows your computer or client-area time zone. Check daylight-saving behavior for time-sensitive work.

Allow editing from the website container

Below the jobs is Allow editing of cron from website container. The panel states that enabling it lets website processes, including PHP and SSH, edit the crontab using the crontab command. The setting is off by default.

This grants an application more control over scheduled execution. Leave it off unless your application or deployment workflow needs that ability and you understand the access it creates. You can manage jobs through this panel without enabling the option.

Check that a task ran

An entry in the list confirms a schedule exists, not that its command succeeded. Check the application’s own task history, expected output, or logs after a scheduled run. For a URL task, verify the application’s recorded result rather than relying only on an HTTP response.

If a WordPress installation already has a scheduled task, review how it triggers WordPress events before adding a second trigger. Avoid assuming every installation has the same default job.

Edit an existing cron job

Use the entry’s edit action, review the current type and schedule, and save the intended change. Check the saved entry and the next run’s result. A schedule change does not prove that an already-running process has stopped.

Remove a cron job

Use the entry’s delete action and verify the command or URL before confirming. Check that it disappears from the list and that the application no longer depends on that schedule.

Removing the entry prevents future scheduled starts through that job. It does not necessarily terminate a process already running or remove schedules maintained by the application elsewhere.

If the task fails, contact support with the website, schedule, time of the expected run, and error text. Remove credentials from any command or URL you include.