When using Group Managed Service Accounts in a multi-tenant environment, an Unschedule error sometimes occurs when you attempt to run a job that was ran in the last 15 minutes. 

The following error occurs in the trace log of the scheduling service: 

This issue occurs because of a race condition inside of the Quartz scheduler in multi-tenant deployments. The issue does not occur in non-MT deployments. When executing a job using Run as, SAS^® Environment Manager schedules the job to run immediately and an unschedule request to remove this trigger. The Quartz scheduler automatically deletes triggers when they have no future runs. These overlapping deletions cause the error to occur when the Quartz scheduler has already deleted the trigger. Note that the failed deletion has no impact on scheduled jobs.

To circumvent this issue, close the error. 

Click the Hot Fix tab in this note for a link to instructions about accessing and applying the software update.

Operating System and Release Information

Viya on Windows: An update for this issue is available for SAS Viya 3.5. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.5 for Windows Deployment Guide at

Viya on Linux: An update for this issue is available for SAS Viya 3.5. For instructions on how to access and apply software updates, see the Updating Your SAS Viya software section in the SAS Viya 3.5 for Linux Deployment Guide at