Hi @BrunoMueller @joeFurbee , It seems that the only way to run correctly the job is starting a session through {{myaddress}}/compute/sessions and then including the session id into job execution body request ({{myaddress}}/jobExecution/jobs). e.g.: {
"name": "AAAAAA",
"description": "Execution of the job",
"jobDefinitionUri": "/jobDefinitions/definitions/aaa11bb22-............",
"arguments":{
"_contextName": "SAS Job Execution compute context",
"_sessionId": "1111aaaa-2222bbb....."
}
} Finally, we are able to obtain the link to the log and we can notice that the autoexec (included into the SAS Job Execution compute context in the SAS environment manager) job is not executed. If we don't follow these steps, we are not able to obtain the log into the returned Json and the result is the following: Should we start a new session every time we need to run the job (otherwise SAS is not able to start it by itself)? There is a way to include the run of autoexec into the request? Thank you again for your support!
... View more