πŸ“Š
Plesk

Setting up a Cron Job in Plesk: Step-by-Step Guide

πŸ“… 7 October 2026 ✏️ 7 October 2026 ⏱ 4 min leestijd

Learn how to set up a cron job in Plesk for automatic tasks like backups and maintenance, with a step-by-step guide and frequently asked questions.

A cron job is an automatically scheduled task that runs on your server at fixed times, such as creating a backup, cleaning up a database, or calling a script. In Plesk, you set this up via a clear interface, without needing to know any command lines. Below you’ll find out what a cron job does exactly, how to set one up, and what to pay attention to.

What is a cron job?

A cron job consists of a command (usually a script or command) and a schedule on which that command is executed. This schedule determines the minute, hour, day of the month, month, and day of the week on which the task runs. For example, you can automatically create a backup every night at 3 a.m., or clean up expired sessions every hour.

The advantage is that you no longer have to perform these tasks manually: the server does the work in the background, even when you’re not active yourself.

ScheduleCron JobScript/Task

Setting up a cron job in Plesk

You set up a cron job via the Plesk panel. You’ll find this under your domain settings for most web hosting packages.

1

Log in to Plesk

Open your Plesk control panel and log in with your user credentials.

2

Go to your domain

Click on Websites & Domains in the menu and select the relevant domain.

3

Open Scheduled Tasks

Find the Scheduled Tasks option (Cron Jobs) in the domain menu and open it.

4

Add a new task

Click on Add Task and enter the command, for example the path to a PHP script.

5

Set the schedule

Choose a preset such as daily or hourly, or set a custom interval via minute, hour, day, month, and weekday.

6

Save and check

Save the task and check the log after the first run to see if everything is working correctly.

πŸ’‘ Tip: Make sure a script doesn’t generate unnecessary output. Many cron jobs send an email every time there’s output; add > /dev/null 2>&1 to the command to prevent this.

Common examples

Cron jobs are used, among other things, for:

  • Automatic backups of files or databases
  • Cleaning up temporary files or logs
  • Sending scheduled emails or newsletters, for example via your business email
  • Refreshing cache for better load times
  • Periodic maintenance of CMS systems such as WordPress

Because cron jobs run directly on the server, at Tandata you benefit from fast processing thanks to LiteSpeed and NVMe storage, even for tasks that process a lot of data.

Preventing and checking for errors

Most cron job issues arise from an incorrect file path, improper file permissions, or a misconfigured schedule. Always check first whether the script works locally before scheduling it. Use the execution log in Plesk to see whether a task has completed successfully, and in case of problems, check whether the path to PHP or another interpreter is correct.

Schedule heavy tasks, such as large backups, outside peak hours and spread multiple cron jobs across different times so they don’t slow each other down. Questions about your hosting environment? Check the knowledge base or contact support.

Frequently Asked Questions

How do I know if my cron job has run?

Open the cron job in Plesk and view the execution log. Here you can see the last execution time and whether it was successful.

What is the smallest interval I can set?

You can run a task every minute, but for most purposes an interval of an hour or a day is sufficient and less taxing on the server.

Can I use multiple cron jobs at the same time?

Yes, you can set up as many tasks as needed. Just make sure heavy tasks don’t run at the same time to avoid performance issues.

My cron job isn’t doing anything, what now?

Check the file path, file permissions, and whether the correct command is being used. Also check the log for error messages.

Can I use cron jobs after switching to another provider?

Yes, after switching to Tandata you can set up your existing cron jobs again in Plesk on your new environment.

Conclusion

Setting up a cron job in Plesk takes just a few minutes and saves you a lot of manual work. Whether it’s backups, maintenance, or email tasks: with the right schedule and command, everything runs automatically in the background. Thanks to LiteSpeed and NVMe storage, these tasks are executed quickly and reliably.

View web hosting β†’

Was dit artikel nuttig?