SAS Viya scheduled jobs occasionally receive an HTTP 401 error when attempting to read the /jobExecution/jobRequests/ endpoint, which causes the job not to run.

When you review the scheduling log (default location: /opt/sas/viya/config/var/log/scheduler/default), an entry similar to the following appears at the time when the job is expected to trigger:

This issue occurs due to the way in which services obtain the signing key that is used to validate tokens. The request to obtain the key has a short time-out and can fail on the first attempt and succeed on the second. Services cache the signing key, so this issue usually occurs only when a service receives a request for the first time after starting or after a long period of inactivity. If jobs are scheduled at these points, they might fail.

To work around the issue for critical jobs, schedule a non-essential job to break this period of inactivity.

This issue is fixed in SAS Viya 3.5 22w34 and later.

Operating System and Release Information