This looks like an issue being experienced by SAS Studio's pre-execution code that runs to produce results that SAS Studio can consume.
My guess would be something in the autoexec or compute server startup commands is putting the SAS session in a state where the studio pre-exec code doesn't function as expected.
_GSFNAME I believe is a temp filename for storing graph output, while _SASWSTEMP_ is set to the compute server's WORK library path.
--
Greg Wootton | Principal Systems Technical Support Engineer