Jet Scheduler Error: "Your scheduled task emails are failing to send" Despite Successful Email Delivery
Issue Summary
Users may encounter persistent error messages in Jet Hub similar to the following:
"Your scheduled task emails are failing to send. Open SMTP settings."
This error occurs even though:
Test emails from SMTP settings are sent successfully.
Scheduled tasks are running and emailing recipients correctly.
Jet Scheduler shows no active errors.
Errors reappear in Jet Hub after refreshing, despite tasks functioning as expected.
Root Cause
This issue typically arises when a scheduled task was initially executed before SMTP settings were properly configured. Even after correcting the settings and rerunning the task successfully, Jet Hub retains the error artifact from the original failure.
Resolution Steps
-
Check error status in SQL
Run the following query in SQL Server Management Studio to identify tasks with error artifacts:
SQL
SELECT * FROM [JetServices].[dbo].[ScheduledTasks]
Show more lines
Look for tasks where ErrorStatus = 1.
Alternatively, to filter only erroring tasks:
SQL
SELECT * FROM ScheduledTasks
WHERE ErrorStatus > 0
``
Show more lines
-
Backup the Jet Service Tier database
Before making any changes, take a backup of the Jet Service Tier database to ensure you can revert if needed.
-
Identify and recreate failing tasks
Review tasks with ErrorStatus = 1.
-
Check for:
Incorrect email addresses
Reports too large to send
Delete and recreate these tasks to remove the error artifact.
-
Optional: Clear error statuses
If you prefer not to delete tasks immediately, you can reset the error status by running the following query in SQL Server Management Studio:
SQL
UPDATE ScheduledTasks
SET ErrorStatus = 0
Show more lines
Then refresh Jet Hub and monitor if the error reappears.
-
Alternative Method: Disable and re-enable tasks
Disable all tasks.
Re-enable only tasks with ErrorStatus = 0.
Run the enabled tasks.
If errors do not reappear, delete and recreate the remaining disabled tasks.
Additional Notes
This error is cosmetic and does not affect task execution or email delivery.
However, it can be misleading for users and support teams, so resolving it improves clarity and user experience.