Schedule Plesk Tasks with the Correct Type and Execution Scope

Plesk Scheduled Tasks runs approved work for a selected subscription. Choose the correct task type, account and environment instead of copying a root package-update command into a website’s schedule.

Create the right kind of task

1. Under the intended subscription, open Websites & Domains > Scheduled Tasks > Add Task.
2. Select a supported type: Run a command, Fetch a URL or Run a PHP script. A URL task takes a URL, not a curl command; PHP tasks use the script path and available interpreter controls appropriate to that form.
3. Enter the intended task details and schedule. Keep schedule fields separate from the command text and confirm the selected timezone in Scheduled Tasks settings.
4. Set a useful description and appropriate notifications. Save and inspect the resulting entry.

Account for the execution environment

On Plesk Linux, command tasks can run in a chroot: paths are interpreted within the subscription’s restricted filesystem, not necessarily the host’s full filesystem. A host-absolute executable path may therefore be unavailable. Ask the administrator about the supported environment instead of disabling the restriction to resolve a file-not-found message. Windows task behavior and executable paths differ.

The old example combining five cron fields with yum update is withdrawn. It confused form input with a complete crontab line, assumed an obsolete package-management environment and treated a subscription task as an appropriate server update mechanism.

Test, activate and monitor separately

Run Now executes the task immediately; it does not merely resume or enable a disabled schedule. Use it only after checking side effects and authorization. Test with safe input, then confirm an actual scheduled run and its application result. A successful manual run does not establish that timing, environment or overlapping invocations are correct.

Use explicit activation/deactivation controls to pause future scheduling where available. Preserve the entry before removing it and confirm application dependencies. Neither deactivation nor removal necessarily terminates a process already running. Protect credentials and logs, and avoid unauthenticated URL jobs that expose administrative actions publicly.

Reference: Plesk task types, chroot paths, timezone and controls.

Reviewed October 15, 2026. Documentation review; no Plesk task, package update or customer script was executed or changed.