Problem Note 70045: The Jobs and Flows Scheduling Interface returns the error "Unable to unschedule trigger while deleting job" after using "Run as"
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:
org.springframework.scheduling.SchedulingException - 'Unable to unschedule trigger [Execute.guid] while deleting job /jobExecution/jobRequests/guid'
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
SAS System | SAS Environment Manager | Linux for x64 | 3.5 | 3.5 | Viya | Viya |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2023-04-28 09:20:04 |
Date Created: | 2023-04-25 05:49:20 |