Record the existing task type, command, runtime, schedule, timezone and notification settings. Identify the application owner and whether another scheduler also launches the same operation. Choose a quiet period for changes to billing, queue or data-processing jobs.

1. Open Scheduled Tasks for the correct subscription and identify the task by command and description.
2. To edit it, open the task and change only the intended fields. Check quoting and paths if an argument or script location changes.
3. To pause it, clear the active setting where available and save. Retain the configuration while you investigate or wait for maintenance to finish.
4. To remove an obsolete task, select that exact entry and use Remove, then confirm the action. Keep a private record if you may need to recreate it.
5. Check the application for an already running job before assuming processing has stopped. Use the application supported stop or drain procedure for active work.

For an edited job, observe the next intended run and confirm its application result. For a disabled or removed job, verify that no new execution begins at the former schedule. Check for duplicate schedules elsewhere if activity continues.

If an edit causes failures, restore the recorded settings and investigate the changed field. If a task keeps launching, confirm you edited the correct subscription and look for another cron, system timer or application scheduler. Avoid killing unknown server processes from a shared-hosting account.

• Creating a scheduled task in Plesk
• Configuring scheduled-task notification email in Plesk
• Creating and downloading a full subscription backup in Plesk
• Creating a scheduled cron task in cPanel

• Plesk: Scheduling Tasks