When the CAS procedure appends to a global table at the same time as that table undergoes a global update, the CAS server can stop responding. In this scenario, the table.update action and the table.append actions can deadlock against each other, which causes CAS to require a restart before it is available again.

If you experience this issue, the CAS logs show that at least one of the table.update actions never completes successfully. The log file does not contain any error to identify this issue. You can find the latest CAS logs in /opt/sas/viya/config/var/log/cas/default/.

In this scenario, the log contains an entry similar to the following after the update:

When the update completes, the CAS log should show something similar to the following indicating that it was successful:

When you encounter this issue, the log never shows the message that the table.update is successful​​​.

This issue causes the CAS server to stop responding and require a restart to temporarily resolve the issue.

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 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