Hi @paterd2 , I'm not sure what timeout you're referring to, but there is a list of compute context attributes here: https://go.documentation.sas.com/doc/en/sasadmincdc/v_068/calsrvpgm/n1jb3fo13t6cdbn16dv8dtfbox7v.htm#p0puuirx6357pyn19li1m698x9ky, for SAS Viya Stable 2025.09, which includes: sessionInactiveTimeout, serverInactiveTimeout, serverLaunchTimeout and taskTimeout.   That page describes serverLaunchTimeout which it says "Specifies how long the service waits for the new server to start up and reach a running state." You'd set this as an attribute in the compute context, following Step 4 of 'Create a Compute Context', here: https://go.documentation.sas.com/doc/en/sasadmincdc/v_068/evfun/p1dkdadd9rkbmdn1fpv562l2p5vy.htm#n0bw1won3jn0axn1brl67tielej1. Here's a screenshot of what that might look like: Example of setting an attribute in a compute context. Here we set the serverLaunchTimeout attribute to 60 seconds for the SAS Studio compute context. I'm not sure AI sites are yet any better at finding this sort of thing than traditional search; in my experience their responses currently seem to contain a seamless blend of correct and totally made-up information! 🙂 Let me know if this isn't quite what you meant for the value you're trying to adjust. It might help us give better suggestions if you explain a bit about the problem you're trying to solve, or how you'd like the behaviour of a component to be tuned/adjusted to produce better or more reliable performance. Thanks! ... View more

This error is an import failure. When importing you first upload a package to the transfer service which would store the package as a large object, then import on that package ID. This error message is saying the package ID we are trying to import is associated with a large object that isn't in the database, so this is sort of the opposite of your initial concern, where we have a reference to the large object in the transfer schema table, but the large object itself isn't present. ... View more

Doug , we now have a case with support. If there is a solution I will inform you. Thank you .   Just to inform you, this is the code we used :  proc http url="https://www.bing.com" method="GET" proxyhost="http://<ourproxy" proxyport=<ourproxyport>; run; If we went to google it works, but for certain sites we got a handshake error. ... View more

Thank you, with this thread and the information you gave me , we are more in control. ... View more

Greg,   thank you. I was sleeping 😉 This works. Regards,   Dik ... View more

--output fulljson authorization list-rules , gives more information, my collegue told me today. If you redirect with > filename.json you have a lot of more output. ... View more

https://communities.sas.com/t5/SAS-Viya/Example-for-sending-email-using-REST-Api/m-p/888375#M1967 contains the answer to your question ... View more

We had to add the following. This changed to default 1 hour.   Authentication timeout: Dit gaat door via Environment manager de volgende instellingen te wijzigen: Configuratie instellingen → SAS Logon Manager   New Configuration → kies voor sas.logon.jwt   vul in bij :   policy.accessTokenValiditySeconds: 28800                     (8 uur)   policy.global.accessTokenValiditySeconds: 28800       (8 uur)   Extract from : Tuning the authentication timeout for long-running jobs (sas.com) With security being at the front and center of most SAS decisions, SAS is gradually reducing the default expiration for Access Tokens from the original value of 10 hours. Shorter-lived tokens reduce the window that a compromised token can be used by an attacker. To avoid possible disruption, this change is being implemented in steps. As of the stable release 2021.2.4 (February 2022), the Access Token default lifetime is decreased to 4 hours; in a later release, it will be further reduced to 1 hour. ... View more

Good afternoon,   is it possible to unzip the file in sas viya, that the "static" reports can be viewed from within sas viya ? Then we can use the security from within viya to let the data be viewed by the right persons.   Regards,    Dik Pater ... View more

In 3.5 you have the ability to just audit read without using HIGH, reports.action.read.state=all. Is this also possible in viya4 ?   ... View more

Using kubectl this info is not available. ... View more

Thanks for your code. I made a studio job..   http://dikpater.blogspot.com/2023/05/sas-viya-cas-cache-cascache-disk-usage.html   ... View more

Thank you @paterd2 for sharing your results. For the example you used that seems quite a compelling case for using GPU processing in certain uses cases.   --Simon   ... View more

Thanks for this article. I have a question, prohibit works, but I can't get the reason being displayed. Reason : u mag dit niet gebruiken, you are not allowed to use this.   Any advice on this ?   Regards ,   Dik Pater   ... View more