Keep Connection Alive in Viya

[engmtcdrm]

Is your feature request related to a problem? Please describe.
The problem is that if you step away from your computer your SAS session can die due to settings in Viya. This can be annoying because then you have to reconnect and rerun code you may have already ran.

Describe the solution you'd like
The solution would either be an option users can set to keep session alive. Maybe it is active by default. I think all that would need to happen is either pinging compute/sessions/{sessionId} using HEAD request or doing the same HEAD request on the job in the session with compute/sessions/{sessionId}/jobs/{jobId}. I'm not 100% on if these endpoints will be sufficient for the session to remain open, but given you're interacting with the session or job would make me think the timer in Viya would reset. It would be similar to resubmitting code to keep the session alive.

Describe alternatives you've considered
You could write a piece of code that ran for a long time while you stepped away, but that is not ideal.

Additional context

Environment
SAS version: Viya 3.5/4

[marclenniger]

Thank you very much for raising this problem!

I experience the same problem on Viya 3.5. And it is the last unsolved issue that is holding us back from rolling out the VScode-Extension for our whole department.