Configuring scheduled-task notification email in Plesk

Choose a monitored recipient that remains reachable if the hosted domain has a problem. Review what the command writes to its output because notifications can include that text. Remove secrets and unnecessary customer information from task logs before enabling frequent reports.

1. Open Scheduled Tasks for the intended subscription and edit the relevant task.
2. Find the notification setting and select the available reporting mode, such as errors only or every execution. Match the choice to the job importance and expected frequency.
3. Enter the custom notification address if offered, or verify the account address used by the selected default. Check spelling and ensure the mailbox can accept external messages.
4. Save the task and perform one safe controlled execution if the job can be run immediately. For a task that changes business data, wait for the next planned execution instead.
5. Check both the task result and the destination mailbox. Configure mail rules so important failures are visible without flooding an unmonitored folder.

Confirm the expected notification arrives with a useful description and no sensitive output. Verify the application result separately. Document who responds to an error so reporting has an operational purpose.

If no email arrives, inspect spam filtering, recipient quota, task output and server mail delivery. Some tools return a successful exit status despite application-level errors, so review their logs and exit behaviour. Do not manufacture a dangerous command failure on production just to test email; use a harmless diagnostic task when authorized.

• Creating a scheduled task in Plesk
• Editing, disabling or removing a scheduled task in Plesk
• Updating the email address on your Plesk profile
• Creating a scheduled cron task in cPanel

• Plesk: Scheduling Tasks