Hosting Hosting features Spanish version

Support article

What a Cron Process Is and How It Works

Learn what a cron process is, what it's used for, and how to schedule automated tasks from cPanel or DirectAdmin on your hosting.

Published: 30/06/2026 Updated: 10/07/2026

Introduction

A cron process lets you run a task automatically on a given date or at a set frequency. It’s common on Linux servers and useful for repetitive work that shouldn’t require manual intervention.

The schedule is stored in a table called crontab, which specifies when each command or script should run.

What a cron process is

Cron is a system service (a daemon) that checks scheduled tasks and runs them in the background.

You can set up an action to run:

  • Every so many minutes.
  • At a specific time.
  • Once a day.
  • On specific days of the week.
  • Once a month.

For example, an application might use cron to process email, generate reports, or run maintenance tasks.

What it’s used for

Cron processes let you automate actions such as:

  • Running an application’s scripts.
  • Generating backups.
  • Cleaning up temporary files.
  • Processing mail or notification queues.
  • Updating information from an external source.
  • Running tasks required by WordPress, PrestaShop, or other applications.

Cron starts the command, but the outcome depends on the script being scheduled correctly and having enough permissions. For practical examples and the cron expression syntax, see what a cronjob is used for.

Availability at miHosting

Cron processes are available on all miHosting hosting plans and can be configured from cPanel or DirectAdmin.

The minimum frequency depends on the plan: on free hosting, once every 10 minutes; on professional hosting plans, every 5 minutes. Scheduling processes too frequently can consume resources, so choose an interval that matches the application’s actual need.

How to set up a cron task

The general procedure is:

  1. Log in to the hosting control panel.
  2. Look for Cron Jobs, Cron Tasks, or Scheduled Tasks.
  3. Pick the frequency.
  4. Enter the command that should run.
  5. Save the task.
  6. Check that the script runs correctly.

Before saving, verify the interpreter path and the file’s full path. An incorrect path is one of the most common causes of failure.

Useful tips

  • Use absolute paths rather than relative ones.
  • Test the command manually when possible.
  • Don’t schedule a task more frequently than necessary.
  • Log the output during the first tests.
  • Avoid putting passwords directly in the command.
  • Make sure the script can’t run several times simultaneously.
  • Include important tasks in your site’s technical documentation.

Common issues

The task shows as created but does nothing

Check the file path, the command, the permissions, and the PHP version used.

I’m getting emails with cron errors

The task is generating output or an error. Review the message and fix the script. You can also redirect the output to a log file.

The process is using too many resources

Increase the interval and review the script’s efficiency. A heavy task run too often can affect hosting performance.

It works when opening the URL, but not from cron

The execution environment may be different. Check paths, variables, permissions, and the command’s dependencies.

Frequently asked questions

Do cron and cronjob mean the same thing?

Cron is the service that runs tasks. A cronjob is each individual scheduled task.

Do I need Linux knowledge?

Not to create a basic task from the panel, but you do need to know the correct command your application requires.

Can I use cron for backups?

Yes, as long as the command and available space are adequate. You should also periodically check that the backups are generated and can be restored.

Can a cron affect performance?

Yes. A task that’s too frequent or too heavy can consume CPU, memory, processes, and disk access.

Conclusion

A cron process automates repetitive tasks on the server. You can set it up from DirectAdmin or cPanel by specifying a frequency and the command that should run.

Use reasonable intervals, check the logs, and always confirm that the process produces the expected result.